[LV] The kernel build process & tools any changes .
Jan-Benedict Glaw
jbglaw at lug-owl.de
Sun Mar 18 23:33:08 CET 2007
On Sun, 2007-03-18 15:04:39 -0700, Mr. James W. Laferriere <babydr at baby-dragons.com> wrote:
> On Sun, 18 Mar 2007 20:56:00 +0100 , Jan-Benedict Glaw <jbglaw at lug-owl.de> Wrote:
> > On Sun, 2007-03-18 12:27:20 -0700, Mr. James W. Laferriere <babydr at baby-dragons.com> wrote:
> > > On Sun, 18 Mar 2007 09:50:39 +0100 Jan-Benedict , Glaw <jbglaw at lug-owl.de> Wrote:
> > > > On Sun, 2007-03-18 00:34:33 -0700, Mr. James W. Laferriere <babydr at baby-dragons.com> wrote:
> > > diff -ruN vax-linux-kernel-200703172115-orig/arch/vax/kernel/diag_led.c vax-linux-kernel/arch/vax/kernel/diag_led.c
> > > --- vax-linux-kernel-200703172115-orig/arch/vax/kernel/diag_led.c 2007-03-17 20:58:34.000000000 -0700
> > > +++ vax-linux-kernel/arch/vax/kernel/diag_led.c 2007-03-17 23:32:39.000000000 -0700
> > > @@ -59,11 +59,11 @@
> > > } else if (is_ka650 ()) {
> > > inverted = 1;
> > > return DIAG_LED_KA650_BASE;
> > > -#if 0
> > > +/* #if 0 */
> > > } else if (is_ka670 ()) {
> > > inverted = 1;
> > > return DIAG_LED_KA670_BASE;
> > > -#endif
> > > +/* #endif */
> > > } else if (is_ka43 ()) {
> > > inverted = 1;
> > > return DIAG_LED_KA43_BASE;
> >
> > Just drop the ifdef stuff. If it works, then, well, it works :) By
> > the way, is it a seven segment display or 8 real LEDs in a row?
>
> Ok , In the next patch . A seven segment display .
> If it makes a differnce . Looks like it might .
I'm just tryin' to get see what it actually is :-) Initially, this
was written for the small desktop machines with a row of LEDs. But now
it's also used to display on those seven segment displays. Maybe it'd
be moved to the LED API that formed some months ago, but I guess we'd
just keep diag_led.c for now.
> > Another question: sgec is a candidate for bugfixing. Does it already
> > work on your KA670 (eg. do you see ethernet traffix like DHCP
> > requests) that originate from the Linux kernel or doesn't it work at
> > all?
>
> I don't know yet linux-kernel base has a bug in it , I think ,
> 'asm/mutex.h' reported missing in 'kernel/mutex.c' per below(**) . My
> linux-2.6.18.3 sources , which have been configured & well I'm using that
> kernel now , doesn't have that file either . I'll check that tree's version
> 'kernel/mutex.c' and see if I can backout whatever change started this .
> Tho a quick prayer for me would be nice as I'll need all the help I can get .
>
> Here's the Killer(*) . The below is the only place in 'kernel/mutex.c'
> that has that include . I have not found in any source tree I have a
> link/file/... that is 'asm/mutex.h' . I do find '$ARCH-asm/mutex.h' files ,
> but none for ARCH=vax even in our vax-linux tree .
> I do not know where to go from here , It is quite outside my abilities
> to decypher . My kernel(i386) builds just fine & runs with the same definitions
> .
We don't have one. Yet :) OTOH, have you tested the path with setting
CONFIG_DEBUG_MUTEXES?
> (/*)...
> vax-linux-kernel$ grep -C3 include kernel/mutex.c
> *
> * Also see Documentation/mutex-design.txt.
> */
> #include <linux/mutex.h>
> #include <linux/sched.h>
> #include <linux/module.h>
> #include <linux/spinlock.h>
> #include <linux/interrupt.h>
>
> /*
> * In the DEBUG case we are using the "NULL fastpath" for mutexes,
> * which forces all calls into the slowpath:
> */
> #ifdef CONFIG_DEBUG_MUTEXES
> # include "mutex-debug.h"
> # include <asm-generic/mutex-null.h>
> #else
> # include "mutex.h"
> # include <asm/mutex.h>
> #endif
>
> /***
> ...(*/)
>
> Also this GAS message seems a little odd to me . I always thought we
> were using gas ? Even using the uclibc .
> ...
> CC kernel/posix-cpu-timers.o
> kernel/posix-cpu-timers.c:1: warning: -g is only supported when using GAS on this processor,
> kernel/posix-cpu-timers.c:1: warning: -g option disabled
> ...
*cough* This is the result of a hack. Adding debugging stuff (DWARF
handling) was reworked upstream. In the mean time, I disabled it
entirely, but placed the warning to remind us. So it's harmless.
You're only missing debugging infos you'd expect if you use the -g
compile option.
>
> (/**)...
> CC kernel/mutex.o
> kernel/mutex.c:1: warning: -g is only supported when using GAS on this processor,
> kernel/mutex.c:1: warning: -g option disabled
> kernel/mutex.c:30:24: error: asm/mutex.h: No such file or directory <<< Here >>>
That needs a fix.
> kernel/mutex.c: In function 'mutex_lock':
> kernel/mutex.c:89: warning: implicit declaration of function '__mutex_fastpath_lock'
> kernel/mutex.c: In function 'mutex_unlock':
> kernel/mutex.c:114: warning: implicit declaration of function '__mutex_fastpath_unlock'
> kernel/mutex.c: In function '__mutex_unlock_slowpath':
> kernel/mutex.c:216: warning: implicit declaration of function '__mutex_slowpath_needs_to_unlock'
> kernel/mutex.c: In function 'mutex_lock_interruptible':
> kernel/mutex.c:259: warning: implicit declaration of function '__mutex_fastpath_lock_retval'
> kernel/mutex.c: In function 'mutex_trylock':
> kernel/mutex.c:311: warning: implicit declaration of function '__mutex_fastpath_trylock'
> make[1]: *** [kernel/mutex.o] Error 1
> make: *** [kernel] Error 2
> ...(**/)
MfG, JBG
--
Jan-Benedict Glaw jbglaw at lug-owl.de +49-172-7608481
Signature of: God put me on earth to accomplish a certain number of
the second : things. Right now I am so far behind I will never die.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lug-owl.de/pipermail/vax-linux/attachments/20070318/38586734/attachment.pgp>
-------------- next part --------------
_______________________________________________
Linux-Vax mailing list
Linux-Vax at pergamentum.com
http://www.pergamentum.com/mailman/listinfo/linux-vax
More information about the Vax-linux
mailing list