Hi Larry,
On Fri, Feb 8, 2013 at 4:11 PM, Larry Baker ba...@usgs.gov wrote:
Steve,
I found this at
http://gcc.gnu.org/onlinedocs/gcc-4.5.4/gcc/M680x0-Options.html. I don't
know if gcc 4.3.2 has this option, but it's worth a try. Maybe you only
have to use this in certain routines? Maybe
On Thu, Feb 14, 2013 at 08:52:10AM -0800, Steve deRosier wrote:
Hi Larry,
On Fri, Feb 8, 2013 at 4:11 PM, Larry Baker ba...@usgs.gov wrote:
Steve,
I found this at
http://gcc.gnu.org/onlinedocs/gcc-4.5.4/gcc/M680x0-Options.html. I don't
know if gcc 4.3.2 has this option, but it's
I'd like to know what is the best way to handle the watchdog timer in
Linux? I've reviewed the docs and the watchdog framework and it's not
really fitting my needs.
The system I'm upgrading turns on the WDT very early in the
boot-loader There is code sprinkled through the boot-loader and then
On Thu, Feb 14, 2013 at 10:34:58AM -0800, Steve deRosier wrote:
[...]
3. Implement some kernel process that takes over automatic periodic
kicking until the real WDT driver is opened the first time by
userspace. Then that process gets disabled.
Unfortunately, I do not remember where I stole
This patch adds the correct CPU name.
Without this, it just displays UNKNOWN at boot time and at '/proc/cpuinfo'.
Regards,
Luis
Signed-off-by: Luis Alves lja...@gmail.com
---
arch/m68k/kernel/setup_no.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/m68k/kernel/setup_no.c
