Re: sysctl interface to bootflags?

From: Thomas Hood (jdthood@mail.com)
Date: Tue Oct 09 2001 - 10:50:08 EST

Sorry, I didn't read your code very carefully before because
I thought it relied on ACPI. Now I understand it better.
It doesn't use /dev/nvram, but /dev/mem.

Here's what happens when I run it.

jdthood@thanatos:~/src/sbf$ gcc sbf.c
jdthood@thanatos:~/src/sbf$ su
Password:
root@thanatos:/home/jdthood/src/sbf# gdb -q ./a.out
(no debugging symbols found)...(gdb) run
Starting program: /mnt/p/home/jdthood/src/sbf/./a.out
BOOT @ 0x07fd0040
CMOS register:51
(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x80489be in outb_p () 

--
Thomas

On Tue, 2001-10-09 at 11:34, Dave Jones wrote:
> On 9 Oct 2001, Thomas Hood wrote:
> 
> > Hi.  I looked at your code and I saw that it depended
> > on ACPI.  Since ACPI doesn't work on my machine, I
> > thought I should look for another solution.  However,
> 
> Huh ? Read the code again.
> Its no more dependant upon ACPI than bootflag.c is.
> The bootflag is pointed at by an ACPI table.
> The code I wrote functions /exactly/ the same on
> a kernel with APM, ACPI or NO power management.
> 
> > Alan now tells me that what I want to do can already
> > be done via /dev/nvram.
> 
> My code _is_ using /dev/nvram !
> 
> regards,
> 
> Dave.
> 
> -- 
> | Dave Jones.        http://www.suse.de/~davej
> | SuSE Labs
> 

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

This archive was generated by hypermail 2b29 : Mon Oct 15 2001 - 21:00:25 EST