All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@googlemail.com>
To: "David Gálvez" <dgalvez75@gmail.com>
Cc: Michael Schmitz <schmitzmic@googlemail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Thorsten Glaser <tg@mirbsd.de>,
	linux-m68k@vger.kernel.org
Subject: Re: EtherNat drivers (was: Re: Atari ROM port ISA)
Date: Fri, 18 May 2012 19:43:10 +1200	[thread overview]
Message-ID: <4FB5FD8E.7030400@gmail.com> (raw)
In-Reply-To: <CAL4YKD6eQN4jOO4LoiDTXLXYBffchPd4Wfjihf-_qnbSZ32+zg@mail.gmail.com>

On 18/05/12 02:49, David Gálvez wrote:
> What interrupt does it report it uses? Do you see the card interrupts
> accumulate in /proc/interrupts?
>
> smc91x: IOADDR 0902c000 doesn't match configuration (300).
> smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre<nico@fluxnic.net>
> eth0: SMC91C11xFD (rev 2) at 0902c000 IRQ 140 [nowait]
>
> /proc/interrupts has this entry:
>
> 140:        68       atari    eth0
That's good - now what is the transmit/receive speed you get with this 
driver on a large file transfer?
>> Just what I'm getting as well. Back to the drawing board. I'll have to get
>> confirmation on the exact addresses being used from the EtherNAT designer.
>>
> The addresses are these:
>
> ISP116X_HCD_ADDR	0x80000016
> ISP116X_HCD_DATA 	0x80000012
I don't think I tried that combination - where did you find that?

Anyway, new test kernel on the way. Won't do anything useful with the 
USB chipset other than hopefully probe it OK.

Thanks,

   Michael

  reply	other threads:[~2012-05-18  7:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 14:49 EtherNat drivers (was: Re: Atari ROM port ISA) David Gálvez
2012-05-18  7:43 ` Michael Schmitz [this message]
2012-05-18 19:26   ` David Gálvez
2012-05-19  4:06     ` Michael Schmitz
2012-05-19  9:30       ` David Gálvez
2012-05-19 21:50         ` Michael Schmitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FB5FD8E.7030400@gmail.com \
    --to=schmitzmic@googlemail.com \
    --cc=dgalvez75@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=tg@mirbsd.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.