From: Randy Dunlap <rdunlap@infradead.org>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: linux-kernel@vger.kernel.org,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
sparclinux@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
linux-parport@lists.infradead.org
Subject: Re: [PATCH] parport_pc: don't allow driver for SPARC32
Date: Thu, 6 Apr 2023 12:51:13 -0700 [thread overview]
Message-ID: <743b5d56-91b1-0b39-44f2-d353a95d59a0@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2304062039260.44308@angie.orcam.me.uk>
On 4/6/23 12:49, Maciej W. Rozycki wrote:
> On Thu, 6 Apr 2023, Randy Dunlap wrote:
>
>> arch/sparc/kernel/ebus.o is only built for SPARC64.
>> ns87303_lock is only built for SPARC64.
>> arch/sparc/include/asm/parport.h says that it is for sparc64.
>> Various documentation on the internet says that ebus is for UltraSPARC
>> systems (64-bit).
>>
>> Therefore don't allow PARPORT_PC to be built for SPARC32.
>
> This looks completely wrong to me, any ordinary PCI parallel port card
> ought just to work as long as you have PCI (S390 is special I'm told).
> What needs to be done is AFAICT just making `parport_pc_find_nonpci_ports'
> in arch/sparc/include/asm/parport.h SPARC64-specific, i.e.:
>
> static int parport_pc_find_nonpci_ports(int autoirq, int autodma)
> {
> return (IS_ENABLED(CONFIG_SPARC64) &&
> platform_driver_register(&ecpp_driver));
> }
>
> or suchlike and let the optimiser get rid of all the unwanted unsupported
> stuff.
Fine, please go ahead with that solution.
--
~Randy
next prev parent reply other threads:[~2023-04-06 19:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 16:05 [PATCH] parport_pc: don't allow driver for SPARC32 Randy Dunlap
2023-04-06 19:28 ` Sam Ravnborg
2023-04-06 19:49 ` Maciej W. Rozycki
2023-04-06 19:51 ` Randy Dunlap [this message]
2023-04-06 20:32 ` Sam Ravnborg
2023-04-06 21:01 ` Maciej W. Rozycki
2023-04-06 21:31 ` Randy Dunlap
2023-04-07 20:03 ` Sam Ravnborg
2023-04-07 21:01 ` Maciej W. Rozycki
2023-04-07 21:10 ` Randy Dunlap
2023-06-18 23:42 ` Maciej W. Rozycki
2023-06-19 0:23 ` Randy Dunlap
2023-06-19 1:29 ` Maciej W. Rozycki
2023-06-19 2:35 ` Randy Dunlap
2023-06-23 15:33 ` David Miller
2023-06-23 17:22 ` Sam Ravnborg
2023-06-23 19:20 ` Randy Dunlap
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=743b5d56-91b1-0b39-44f2-d353a95d59a0@infradead.org \
--to=rdunlap@infradead.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=macro@orcam.me.uk \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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;
as well as URLs for NNTP newsgroup(s).