[kbuild-devel] Re: [PATCH] [kbuild] Possibility to sanely link against off-directory .so

2002-11-06 Thread Sam Ravnborg
On Wed, Nov 06, 2002 at 07:52:30PM +0100, Petr Baudis wrote:
>   Hello,
> 
>   this patch (against 2.5.46) introduces two special variables which make it
> actually possible to have .so as the only product of build in some directory
> and to link something against .so being built in another directory. The
> variable host-cshlib-extra makes it possible to explicitly mention shared
> objects to be built and the variable $(-linkobjs) allows user to specify
> additional objects to link  against, while not creating any dependencies
> of  on the objects.
> 
>   The changes are minimal while dramatically extending possibilities for
> messing with the shared objects and they should have no unwanted side-effects,
> and it appears to actually work for me. Please apply.

There is only one user of shared libaries today, thats Kconfig.
And Kconfig is the only user of C++ as well.

There is quite a lot of added complexity in Makefile.lib + Makefile.build
only to support this. Being the one that introduced it, I would like to
see it go away again.
Rationale behind this is that the current added complexity has an penalty
when compiling a kernel, and I would like to move the complexity to
the only user.

Care to try that approach?

Sam


---
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
___
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel



Re: [kbuild-devel] string and if

2002-11-06 Thread Roman Zippel
Robert Schwebel wrote:

> config GNU_TARGET
> string "i386-linux" if OPT_I386
> string "i486-linux" if OPT_I486
> string "i686-linux" if OPT_I686
> string "arm-linux"  if OPT_ARM4
> default "-not configured-"
> 
> for example give
> 
>   GNU_TARGET="arm-linux"
> 
> in case OPT_ARM4=y? It doesn't work, I get "-not configured-", no matter
> which option is defined.

Above isn't valid. You define multiple user prompts and at most only one
is allowed. If you want a derived variable, it should look like this:

config GNU_TARGET
string
default "i386-linux" if OPT_I386
default "i486-linux" if OPT_I486
default "i686-linux" if OPT_I686
default "arm-linux"  if OPT_ARM4
default "-not configured-"

bye, Roman


---
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
___
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel



Re: [kbuild-devel] [upatch] tweak for !KBUILD_VERBOSE output

2002-11-06 Thread Kai Germaschewski
On Mon, 4 Nov 2002, Peter Samuelson wrote:

> > Now we only need to convince Peter.
> 
> I just sent you a patch with all [M], so I guess you can consider me
> sufficiently convinced.  I'm not, really, but it's hardly an important
> issue, so I figured I'd stop wasting all of our time.  Besides, I am
> outnumbered 2-1. (:

Okay, as you're not seriously mad, I consider you convinced ;)

> I think the world would have been better off if 5 years ago we had
> decided to come up with a new suffix (say ".ko") for kernel modules.
> Sure they are object files, but they are *more* than that.  (And some
> day we may want to use ... who knows? shared libraries?)  The biggest
> advantage would have been avoiding crap like "sr_mod.o" in favor of the
> much saner "sr.ko"
> 
> As a side effect, this would have made the present issue go away,
> because there would be no need for the additional information: .ko ==
> final module, .o == not final module.
> 
> At this point I suspect it is about 5 years too late to propose my .ko
> change.  Too much user confusion.  Too bad.

May actually still happen together with Rusty's new module stuff, though 
I'm not sure if that's 2.5 or 2.7 material...

--Kai




---
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
___
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel



Re: [kbuild-devel] A hole in kernel space!

2002-11-06 Thread Peter Samuelson

Note: this question really belongs on <[EMAIL PROTECTED]>.

[Pannaga Bhushan]
> I am looking for a setup where I need to have a certain amount
> of data always available to the kernel. The size of data I am looking
> at is abt 40MB(preferably, but I will settle for 20MB too) . So the
> normal kmalloc will not help me. So what I did was, I created a hole
> in kernel space by putting the following line in vmlinux.lds
>
> ALIGN(4096);
>  __hole_start = .;
> . = . + 0xmy_size;
>  __hole_end = .;

I assume you also tried the old-fashioned C method:

  #include 
  static char __hole_start[0xmy_size] __attribute__((__aligned__(PAGE_SIZE)));

Did that not work either?

> 1.   Is there any other way I can get to keep 40MB(or even 20MB) of
> contiguous kernel memory space ?

There used to be a patch out there called `bigphysarea' - look around,
perhaps someone is still maintaining it.  It should do what you want.

> 2.Abt the 17MB hole, I am able to use after the   _end = .;
>  is this 17MB really there in kernel image?('cos it isn't in
> any segment and also it appears after _end).

I doubt it is accessible, but that is really uninformed speculation on
my part.

> (basically, i want by data in kernel space always available to kernel
> without having to bother abt swapping the pages back)

User space could allocate this space and then call mlockall().  That
does not guarantee *physically* contiguous space, though, and is only
accessible within to the address space of that one process.

Peter


---
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
___
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel



[kbuild-devel] string and if

2002-11-06 Thread Robert Schwebel
Hi, 

I'm currently trying to port a program which used CML1 to lkc/kconfig.
Now I need a string variable which is dependend on a bool. Shouldn't
this: 

config GNU_TARGET
string "i386-linux" if OPT_I386
string "i486-linux" if OPT_I486
string "i686-linux" if OPT_I686
string "arm-linux"  if OPT_ARM4
default "-not configured-"

for example give 

  GNU_TARGET="arm-linux" 

in case OPT_ARM4=y? It doesn't work, I get "-not configured-", no matter
which option is defined. 

This is basically lkc-1.2, taken from Roman's web site. 

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Braunschweiger Str. 79,  31134 Hildesheim, Germany
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
Phone: +49-5121-28619-0 |  Fax: +49-5121-28619-4

Visit us at the SPS/IPC/Drives 2002 in Nuernberg!
   Hall 5, Booth 154 +++ Please contact us for details.


---
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
___
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel