linux-kernel - Re: [RFC][PATCH] LED Class support for Soekris net48xx

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:	Sun, 23 Jul 2006 14:46:55 +0100
From:	Chris Boot <bootc@...tc.net>
To:	Eric Lammerts <eric@...merts.org>
Cc:	kernel list <linux-kernel@...r.kernel.org>,
	soekris-tech@...ts.soekris.com
Subject: Re: [RFC][PATCH] LED Class support for Soekris net48xx

Eric Lammerts wrote:
> Chris Boot wrote:
>> I'd love to find a way of detecting a Soekris net48xx device
>  > but there is no DMI or any Soekris-specific PCI devices.
> 
> You could do ugly things like this:
> 
>         int i;
>         char *bios = __va(0xf0000);
> 
>         for(i = 0; i < 0x10000 - 19; i++) {
>                 if(memcmp(bios + i, "Soekris Engineering", 19) == 0) {
>                         printk("soekris string found at 0x%x\n", i);
>                 }
>         }
> 
> The string "net4801" is also in there (although I'm using a 4826).
> 
> If anyone knows a better way, I'd like to know it too.

Hmm, very ugly indeed! Where did you dig those offsets up from? Are they likely 
to work properly in non-Soekris devices? I think just relying on people not 
loading the module when not in the correct hardware is probably the best option 
at the moment...

Chris

-- 
Chris Boot
bootc@...tc.net
http://www.bootc.net/
-
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/