linux-kernel - Re: [PATCH] pci-quirks: HP hides SMBus controller in Compaq nx9500 laptops

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] [day] [month] [year] [list]

Date:	Tue, 6 Jan 2009 13:43:31 +0100
From:	Michał Mirosław <mirq-linux@...e.qmqm.pl>
To:	Pavel Machek <pavel@...e.cz>
Cc:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH] pci-quirks: HP hides SMBus controller in Compaq nx9500 laptops

On Tue, Jan 06, 2009 at 09:41:21AM +0100, Pavel Machek wrote:
> > rechot ~ # i2cdetect -a 0
> > WARNING! This program can confuse your I2C bus, cause data loss and worse!
> > I will probe file /dev/i2c-0.
> > I will probe address range 0x00-0x7f.
> > Continue? [Y/n] y
> >           0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> >      00: -- -- -- -- -- -- -- -- 08 -- -- -- -- -- -- --
> >      10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> >      20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> >      30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> >      40: -- -- -- -- 44 -- -- -- -- -- -- -- -- -- -- --
> >      50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> >      60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- --
> >      70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> > 
> > I observed no ill effects after scanning the bus, but YMMV.
> > 
> > Using the bus is probably not a good idea if the SMM code is really using
> > it, and so it might be better if this patch lies in the archives for now.
> > After I get the BIOS flashing to work I'll look into this.
> I'm not saying SMM code _does_ use it... I just don't know, and
> reading DSDT will not tell me (or you).

But it is likely, isn't it? By 'looking into this' I meant that I will
take the BIOS apart again, disassemble it and check whatever it is that
the vendor is hiding. I'll repost this patch if it turns out there's
nothing to worry about.

Anyway - if someone wants to do the digging sooner, I can share
what I already know (including some documentation, tools and BIOS images
I found using Google).

Best Regards,
Michal Miroslaw

--
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/