Re: 2.6.3 - 8139too timeout debug info

[OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>]

OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:

> Christian Gut <cycloon@is-root.org> writes:
> 
> > On Tue, 23 Mar 2004, OGAWA Hirofumi wrote:
> > 
> > > Jeff Garzik <jgarzik@pobox.com> writes:
> > > > What was the final resolution of the 8139too debugging?
> > > 
> > > http://marc.theaimsgroup.com/?l=linux-kernel&m=107919285122190&w=2
> > > The cause of his problem was BIOS configuration. It was edge-trigger.
> > 
> > not sure if that was the only reason. 2.6.3 and everything up breaks the
> > rtl nic in my laptop and i cant configure anything like edge-trigger in
> > my bios.

This problem was also edge-triggered interrupt. In his case, ACPI
enable fixes it.

Looks like APCI does the following in acpi_pci_irq_enable(),

	/* 
	 * Make sure all (legacy) PCI IRQs are set as level-triggered.
	 */
#ifdef CONFIG_X86
	{
		static u16 irq_mask;
		if ((dev->irq < 16) &&  !((1 << dev->irq) & irq_mask)) {
			ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Setting IRQ %d as level-triggered\n", dev->irq));
			irq_mask |= (1 << dev->irq);
			eisa_set_level_irq(dev->irq);
		}
	}
#endif

This one is useful as workaround. But I think eisa_set_level_irq() is
not enough for doing this, because looks like the some chips needs
additional setting.

Probably we need the proper interface... Ummm..
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>