Erich,
> >
> >I talked to the other Bering-uClibc developers, if the tests with wd1100
> >support go well for "standard" hardware and it wors for you with
> >pcengines, expect the "wd1100" kernel and support in Bering-uClibc 2.0rc2.
>
> Hey, sounds great. I doubt though, that wd1100.o will do a
Eric
At 07:55 09.10.2003 +, you wrote:
Hi Erich,
...
> Will let you know when I know the right answers.
>
Ok thanks.
I talked to the other Bering-uClibc developers, if the tests with wd1100
support go well for "standard" hardware and it wors for you with
pcengines, expect the "wd1100" k
Eric
Eric Spakman wrote the following at 19:44 05.10.2003:
Erich,
It's indeed a little weird and I never saw it before (maybe I just
didn't notice it before)
Anyway, I have a kernel, modules.lrp and updated
/etc/init.d/hwclock.
hwclock ?? watchdog
The kernel and modules.lrp can be used with eith
Eric
A bit of analysis on this snippet:
bsetup.s: Assembler messages:
bsetup.s:2393: Warning: value 0x37ff truncated to 0x37ff
>> ramdisk_max:.long (-(0xC000)-(128 << 20))-1 # (Header
version 0x0203 or later)
this results in a value of: 37FF
which in a lon
Erich
Eric Spakman wrote the following at 15:13 02.10.2003:
Erich,
>
> Funny, what compiler version are you using?
>
GCC-2.95, but I compiled it from within VMware. I will try a recompile
with a "real" computer.
I compile on a 'real' computer, although not with its native compiler.
Here are m
Eric
At 21:29 30.09.2003 +0200, Eric Spakman wrote:
Erich,
> >-load one of the drivers somewhere in the boot process (and store
> >them in one of the lrps)
>
> I believe we identified modules.lrp as the best place, but then ... see
below
>
> >That always imply a change in the base line, because
Erich,
> >-load one of the drivers somewhere in the boot process (and store
> >them in one of the lrps)
>
> I believe we identified modules.lrp as the best place, but then ... see below
>
> >That always imply a change in the base line, because the softdog
> >module needs to get loaded somewhere
Eric
let me try cover your last 2 messages in one
Let me see if I get your proposal right:
-compile a new kernel with softdog and wd1100 as modules
right
-load one of the drivers somewhere in the boot process (and store
them in one of the lrps)
I believe we identified modules.lrp as the best pla
Erich,
> thanks for replying.
>
> At 12:24 30.09.2003 +0200, Eric Spakman wrote:
> >Hello Erich,
> >
> >I took a look at the driver source, but it looks like it also need a
> >/dev/wd entry to function.
>
> Where did you take the driver from, I posted the new driver at the end of
> my developme
Eric
thanks for replying.
At 12:24 30.09.2003 +0200, Eric Spakman wrote:
Hello Erich,
I took a look at the driver source, but it looks like it also need a
/dev/wd entry to function.
Where did you take the driver from, I posted the new driver at the end of
my development cycle. Unless you took i
Hello Erich,
I took a look at the driver source, but it looks like it also need a
/dev/wd entry to function. Looking at the Bering watchdog source
(which is a very basic implementation looking only at /dev/watchdog)
I don't see how this can work.
I also think that loading a driver in /etc/init.d/w
Hi folks
Some time ago I posted a request to include support for the pcengines wrap
board here. Unfortunately there has not been much of an echo. Could the
Bering crews please tell me if they would consider to include the necessary
modules and mods into the base line.
Basically there are 2 pre
12 matches
Mail list logo
