public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: [PATCH] USB: isp116x: isa_rom_*() calls should depend on CONFIG_ATARI_ROM_ISA
Date: Tue, 09 Sep 2014 20:33:22 +1200	[thread overview]
Message-ID: <540EBB52.9080006@gmail.com> (raw)
In-Reply-To: <CAMuHMdWZGpbVTvJypNXejpEQRUrSQbqbMCx=-Sy=7zQiPPsAFQ@mail.gmail.com>

Hi Geert,

>>> Upon closer look, I think I broke the NetUSBee support if
> Aarghl, I meant EtherNAT. Sorry, I misread who's using ATARI ROM ISA and
> who's using memory mapped I/O.

Makes sense now.

> I had left out the isa_rom_*() clutter, as I was really talking about
> EtherNAT.

OK, so we are on the same version after all.

>
>> need to ensure CONFIG_ATARI_ROM_ISA is set for NetUSBee though. Maybe select
>> ATARI_ROM_ISA if ATARI_USB is selected in Kconfig.bus, just to be safe?
> But ATARI_ROM_ISA is not needed for EtherNAT? So I'd rather not add this
> dependency.

Correct - compiling for EtherNAT only would pull in ROM support where it 
is not in fact needed. Might do more harm than good.

> This does mean we have to distinguish in isp116x.h between three case, right?
>    - #ifdef CONFIG_ATARI_ROM_ISA=y: handle both
>    - elif defined(CONFIG_ATARI): handle EtherNAT only
>    - else: others

If we want to avoid triggering the same compile error again, yes. To 
optimize away the clutter, doubly yes. I doubt someone would want to 
build for NetUSBee only - there is no config option that would allow 
that at present. We did discuss simplifying the option mess at some 
stage (for EtherNEC or EtherNAT) - I would be hesitant to add NetUSBee 
or EtherNAT specific options back in.

>> The help text there could use an update as well - mention NetUSBee as user
>> of ATARI_ROM_ISA in addition to EtherNEC, and mention the need for
>> ATARI_ROM_ISA for the NetUSBee in the ATARI_USB section, if you rather not
>> pre-select ATARI_ROM_ISA there. Does this make sense?
> Yes it does.

Shall I submit a help text patch, or are you happy to do that?

Cheers,

     Michael

  reply	other threads:[~2014-09-09  8:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 16:16 [PATCH] USB: isp116x: isa_rom_*() calls should depend on CONFIG_ATARI_ROM_ISA Geert Uytterhoeven
2014-08-30  1:25 ` Michael Schmitz
2014-09-08  7:45   ` Geert Uytterhoeven
2014-09-08  8:47     ` Michael Schmitz
2014-09-08  9:04       ` Geert Uytterhoeven
2014-09-09  8:33         ` Michael Schmitz [this message]
2014-09-09  8:38           ` Geert Uytterhoeven

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=540EBB52.9080006@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    /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