Subject: Re: lkm device drivers under NetBSD/Alpha
To: Chris G Demetriou <BALVENIE.PDL.CS.CMU.EDU!Chris_G_Demetriou@werple.net.au>
From: John Birrell <firstname.lastname@example.org>
Date: 12/14/1995 18:18:00
> > I just tried using modload on a device driver. 8-(. Seems that modload is
> > (not surprisingly) hard-coded to match the linker switches of ld in the main
> > source tree. The GNU ld used by NetBSD/Alpha treats -T differently.
> it's about 15 minutes to fix this and the other 'easy' problems in
> The bigger problem is the fact that it Really Really Really Wants
> a.out, and NetBSD/Alpha uses ECOFF...
Too true. Considering that I need (want) lkm's to work, are there technical
reasons that make getting modload to do ECOFF unachievable (by me, not
_you_ 8-) ??? I guess the question I'm asking is: does the concept of
modload work with ECOFF files?
And is this likely to be less or more difficult than getting gdb to work
on NetBSD/Alpha? 8-)
> At one point, i fixed the easy parts (e.g. getting the args to 'ld'
> right), but the fixes were so easy that i just tossed them when i
> realized that the a.out problem existed. (actually, i think i might
> have done them several times, because i'm forgetful, but that's
> another story... 8-)
> > I guess this means that modload will need some '#ifdef __alpha's?
> no, '__alpha__'s. any maybe '__pmax__'s, depending on what tools
> exactly they use. (at least some of the changes should be common.)
Is the place for all these #ifdefs modload.c, or arch specific files?
John Birrell CIMlogic Pty Ltd
email@example.com 119 Cecil Street
Ph +61 3 9690 9600 South Melbourne Vic 3205
Fax +61 3 9690 6650 Australia
Mob +61 18 353 137