by Ulrich Wind » Tue, 27 Feb 2001 16:00:04
browsing the sources for some problem I wondered why nvram.c uses a
static spinlock named rtc_lock, hiding the global one.
Regards,
Ulrich
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
by Alan Co » Tue, 27 Feb 2001 23:50:04
It only does that for the atari, where the driver isnt used by other thingsQuote:> browsing the sources for some problem I wondered why nvram.c uses a
> static spinlock named rtc_lock, hiding the global one.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
by Alan Co » Tue, 27 Feb 2001 23:50:05
Read carefullyQuote:> > It only does that for the atari, where the driver isnt used by other things
> Hmm.. are there different nvram.c drivers? I noticed that SuSE 7.1
> loads that driver in i386....
TheQuote:> * This driver allows you to access the contents of the non-volatile
> memory in
> * the mc146818rtc.h real-time clock. This chip is built into all PCs
> and into
> * many Atari machines. In the former it's called "CMOS-RAM", in the
> latter
> * "NVRAM" (NV stands for non-volatile).
static spinlock_t
is in the ATARI specific section
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
by Ulrich Wind » Wed, 28 Feb 2001 00:00:06
Hmm.. are there different nvram.c drivers? I noticed that SuSE 7.1Quote:> > browsing the sources for some problem I wondered why nvram.c uses a
> > static spinlock named rtc_lock, hiding the global one.
> It only does that for the atari, where the driver isnt used by other things
Also doesn't look a lot like Atari:
* This driver allows you to access the contents of the non-volatile
memory in
* the mc146818rtc.h real-time clock. This chip is built into all PCs
and into
* many Atari machines. In the former it's called "CMOS-RAM", in the
latter
* "NVRAM" (NV stands for non-volatile).
Regards,
Ulrich
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hi,
I misconfigured my Linux 2.2.18 kernel: forgot to include the network
device, which is kind of essential for a machine with nfs-root.....
So it just sat there waiting for the root floppy... Then I recompiled
my kernel, but when I came back to the console I saw:
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
scsi : 0 hosts.
scsi : detected total.
IP-Config: No network devices available
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
(Warning, this kernel has no ramdisk support)
VFS: Insert root floppy and press ENTER
end_request: I/O error, dev 02:00 (floppy), sector 0
Unable to handle kernel NULL pointer dereference at virtual address 00000008
current->tss.cr3 = 00101000, %cr3 = 00101000
If someone has some desire to fix something, you can try to find/fix
this.
The recompile of course overwrote the symbol table from the kernel
that I was running...
Roger.
--
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
2. Drivers for VIA 8400 video chipset
4. problem with echoing in alias
5. Enabling Firewall on Redhat 9 (with 2.2.18) ?
6. Getting full name of a directory
7. Mixing UDMA33/66 drives, VIA IDE, Linux 2.2.18
8. "visual studio" for linux ??
9. PROBLEM: DHCP doesn't work in 2.2.18?
10. 2.2.18 + Scheduling in interrupt
11. kernel 2.2.18 compile fails on slackware
12. KERNEL PANIC in 2.2.17 and 2.2.18
13. Big trouble trying to compile a 2.2.18 kernel