From: Russell King <rmk@arm.linux.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pavel Roskin <proski@gnu.org>, Tim Small <tim@buttersideup.com>,
linux-pcmcia@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: TI yenta-alikes (was: ToPIC specific init for yenta_socket)
Date: Thu, 7 Aug 2003 14:12:27 +0100 [thread overview]
Message-ID: <20030807141227.B25908@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1060258695.3123.36.camel@dhcp22.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Thu, Aug 07, 2003 at 01:18:15PM +0100
On Thu, Aug 07, 2003 at 01:18:15PM +0100, Alan Cox wrote:
> On Iau, 2003-08-07 at 10:02, Russell King wrote:
> > doing is *wrong*. The only people who know whether the pin has been
> > wired for INTA or IRQ3 are the _designers_ of the hardware, not the
> > Linux kernel.
>
> That assumes the yenta controller isnt hotplugged.
Even if it is hot plugged, the _kernel_ doesn't have the hardware
design information to make the correct decision about the value to
program into that register.
However, luckily, some devices load the IRQMUX register from an
EEPROM, so it should be correctly setup.
> > Currently, the Linux kernel assumes a "greater than designers" approach
> > to fiddling with the registers which control the function of these pins,
> > and so far I've seen:
> >
> > - changing the mode from serial PCI interrupts to parallel PCI interrupts
> > causes the machine to lock hard (since some cardbus controllers use the
> > same physical pins for both functions.)
>
> Basically we got burned by changing the IRQMUX register rather than just
> using it as an information source.
Different register - that was the device control register...
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-08-07 13:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 18:25 [PATCH 2.6] ToPIC specific init for yenta_socket Daniel Ritz
2003-08-06 18:44 ` Russell King
2003-08-06 19:07 ` Pavel Roskin
2003-08-06 19:32 ` Russell King
2003-08-06 20:39 ` Pavel Roskin
2003-08-06 22:23 ` TI yenta-alikes (was: ToPIC specific init for yenta_socket) Tim Small
2003-08-07 4:01 ` Pavel Roskin
2003-08-07 9:02 ` Russell King
2003-08-07 12:18 ` Alan Cox
2003-08-07 13:02 ` TI yenta-alikes Tim Small
2003-08-07 13:16 ` Russell King
2003-08-07 14:00 ` Alan Cox
2003-08-07 14:38 ` Russell King
2003-08-07 14:49 ` Tim Small
2003-08-07 13:12 ` Russell King [this message]
2003-08-07 9:18 ` Tim Small
2003-08-06 20:50 ` [PATCH 2.6] ToPIC specific init for yenta_socket Daniel Ritz
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=20030807141227.B25908@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=proski@gnu.org \
--cc=tim@buttersideup.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