From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
Linux/m68k <linux-m68k@vger.kernel.org>,
debian m68k <debian-68k@lists.debian.org>,
"David S. Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] m68k/atari: EtherNEC - ethernet support (ne),>
Date: Wed, 13 Aug 2014 20:37:33 +1200 [thread overview]
Message-ID: <53EB23CD.2060101@gmail.com> (raw)
In-Reply-To: <CAMuHMdWqXPf_1a1b=VGGayS2y2DPEibeOpFMFZth6KZUMue6BQ@mail.gmail.com>
Hi Geert,
>
>> Would you be OK if I expanded the comment like this?
>>
>> /* ne.c is used on m68k Atari and Q40 computers - the Atari ROM-port
>> adapter is 8-bit, Q40 uses ISA */
>>
>
> DaveM already applied it to his tree, and sent a pull request to Linus.
>
OK - won't resend then unless explicitly requested.
Many thanks, Dave!
>> This would limit the runtime test to the case where it is actually
>> needed (untested):
>>
>> #elif defined(CONFIG_ATARI) && defined(CONFIG_Q40)
>> /* multiplatform m68k kernel - the Atari ROM-port adapter is 8-bit,
>> Q40 uses ISA */
>> # define DCR_VAL (MACH_IS_ATARI ? 0x48 : 0x49)
>> #elif defined(CONFIG_ATARI) /* no Q40 support - 8-bit mode on Atari ROM port */
>> # define DCR_VAL 0x48
>> #else
>> # define DCR_VAL 0x49
>> #endif
>>
>
> MACH_IS_ATARI already evaluates to a constant on single-platform
> kernels, so this is optimized at compile time.
> Hence there's not really a need for this.
>
I was hoping it would. More of an attempt to make the logic easier to
understand, but a comment would be sufficient (and avoid redundancy).
>> Are there any other m68k platforms that use the ne.c driver, Geert?
>> apne, hydra and zorro8390 all have their own separate drivers - any
>> others?
>>
>
> Not that I'm aware of. Only Q40 has CONFIG_NE2000 in defconfig.
>
Good - we can finally put this one to rest.
Cheers,
Michael
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
prev parent reply other threads:[~2014-08-13 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 2:02 (unknown), Michael Schmitz
2014-08-12 14:55 ` [PATCH] m68k/atari: EtherNEC - ethernet support (ne),> Paul Gortmaker
2014-08-12 15:16 ` Geert Uytterhoeven
2014-08-12 21:40 ` Michael Schmitz
2014-08-13 7:15 ` Geert Uytterhoeven
2014-08-13 8:37 ` Michael Schmitz [this message]
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=53EB23CD.2060101@gmail.com \
--to=schmitzmic@gmail.com \
--cc=davem@davemloft.net \
--cc=debian-68k@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox