Frank Kotler wrote:
> Frank Kotler wrote:
>
> ...
>> Let me look at that DMIDecode... Maybe it'll give me some ideas...
>> Meantime, "don't give up" is good advice! :)
>
> I take it back. "Give up!" :)
>
> Seriously, what I see in this code opens "/dev/mem" and memmaps it. Not
> suitable at all to load from a bootsector. We may be able to crib some
> "magic numbers" from it... maybe some "text"... Has Linux "done
> something" to put this stuff in "/dev/mem", or is it "just there" at
> bootup?
Naw, it's "just there". This little dos .com file finds the stuff that
DMIDecode apparently decodes...
org 100h
mov ax, 0F000h
mov ds, ax
xor si, si
search:
cmp dword [si], '_SM_'
jz found
add si, 16
cmp si, 0FFF0h
jnz search
notfound:
; complain
jmp exit
found:
mov ah, 0Eh
mov bx, 7
mov cx, 600h
show:
lodsb
cmp al, ' '
jae okay
mov al, '.'
okay:
int 10h
loop show
exit:
ret
Perhaps you can beat that C code into something that can be loaded from
your bootsector - how good are you at this? I think *I'd* find it easier
to do it in asm, using the C code as a guideline - we're not going to
need to mmap "/dev/mem"... And specs from here:
http://www.dmtf.org/standards/smbios/
Beginning to look more "tedious" than "hard". What do you actually need
to do? Are you committed to a C kernel? Need the complete display that
the C code gives us? Or do you just need certain information about the
hardware?
Best,
Frank
|
