lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 7 Jun 2007 09:44:07 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	"Linus Walleij (LD/EAB)" <linus.walleij@...csson.com>
Cc:	"Samuel Ortiz" <samuel@...tiz.org>, arvidjaar@...l.ru,
	linux-kernel@...r.kernel.org,
	"Michal Piotrowski" <michal.k.k.piotrowski@...il.com>,
	ambx1@....rr.com
Subject: Re: 2.6.22-rc: regression: no irda0 interface (2.6.21 was OK), smsc does not find chip

On Thursday 07 June 2007 06:23:58 am Linus Walleij (LD/EAB) wrote:
> Björn wrote:
> > Something's wrong with this strategy.  The BIOS is telling us 
> > that an SMCf010 device is present, active, and responds at io 
> > ports 0x100-0x107 and 0x2e8-0x2ef.  The fact that it happens 
> > to be on the other side of an ISA or LPC bridge should be 
> > immaterial to the OS driver.
> 
> Yes, ideally. Yes of course it is wrong, or from a platonic
> perspective. If nobody wrote buggy BIOS:es there would be no
> problem.

Yup, I agree that we will always need to work around BIOS bugs.

But smsc-ircc2 contains a *lot* of preconfigure stuff.  I'm
skeptical that all of it is really to work around BIOS bugs.
I think it's more likely that Linux just isn't using the PNP
info correctly or drivers for other southbridge devices are
getting in the way.

> There is some history in the preconfigure functions:
> these come from the smcinit tool (see http://irda.sourceforge.net/smcinit/),

Thanks for the pointer.  I'll read over that and see if I can
find a laptop to play with.

Bjorn

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ