TI yenta-alikes (was: ToPIC specific init for yenta_socket)

Russell King rmk at arm.linux.org.uk
Thu Aug 7 15:12:27 BST 2003

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 at arm.linux.org.uk)                The developer of ARM Linux

More information about the linux-pcmcia mailing list