linux-kernel - How should I handle device with two PNP-BIOS ids?

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

Date:	Mon, 26 Jan 2009 10:21:29 +0100
From:	"Krzysztof Helt" <krzysztof.h1@...pl>
To:	linux-kernel@...r.kernel.org
Subject: How should I handle device with two PNP-BIOS ids?

Hi,

There is brain-damaged sound chip which is identified by two separate 
PNP ids. This was done probably to keep backward compatibility (the 
first id is for the old type of chip, the second id gives only one 
additional io range required for newer chips).

How to does properly detect such a device using the PNP framework?
Is there any way to specify two PNP ids as one device?

Is it better to iterate over a pnpbios protocol of the first device to 
find out if there is the second id? This way has an advantage that I can 
distinguish between old chip (no the second id found) and newer chips 
(the second id found).

Thank you in advance answer,
Krzysztof

----------------------------------------------------
Kate Winslet i Leonardo DiCaprio znowu razem na ekranie!
DROGA DO SZCZĘŚCIA - w kinach od 30 stycznia. 
Zobacz zwiastun: http://klik.wp.pl/?adr=http%3A%2F%2Fcorto.www.wp.pl%2Fas%2Fszczescie.html&sid=624

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