How To Compile Modules? Options

[Capn_Fish]

I would like to be able to compile modules for pdaXrom, but don't know how. Could somebody post a how-to? Unless I'm mistaken, the process is different on pdaX than on a normal box. Links to the stuff necessary would be great.

Hopefully this isn't horribly obvious.

Thanks in advance.

[Meanie]

I would like to be able to compile modules for pdaXrom, but don't know how. Could somebody post a how-to? Unless I'm mistaken, the process is different on pdaX than on a normal box. Links to the stuff necessary would be great.

Hopefully this isn't horribly obvious.

Thanks in advance.

for 2.6.x kernel you need to add the kernel headers to gcc 3.4.6
for 2.4.x kernel you need to use gcc 2.95.x (with fpa) and add the kernel headers for the appropriate model, ie Cxx00 use 2.4.20 kernel whereas cxx0 use 2.4.18 something kernel.

[Capn_Fish]

I feel like I've asked this before, but how do I get the kernel headers? And where exactly do I put them?

Thanks, and sorry for the (potentially) repeated question(s).

[Capn_Fish]

Could somebody please post the answers to the questions above? I'm fairly certain somebody here knows the answers...

[Meanie]

I feel like I've asked this before, but how do I get the kernel headers? And where exactly do I put them?

Thanks, and sorry for the (potentially) repeated question(s).

http://distro.ibiblio.org/pub/linux/distri...ns/pdaxrom/src/

you need to configure the kernel but instead of compiling it, just copy the entire include subtree and whack it under the gcc include tree or symlink it....

[Capn_Fish]

After trying to configure the kernel, I have a few more questions:

-Can I do the configure part on a desktop?

-Does it matter what I configure it with?

Thanks.

[louigi600]

1)install pdaxrom builder on a pc or virtual machine
2)follor the steps on note 101 upto when you start to actually build the romm (make all)
3)run make kernel_get
4)run make kernel_prepare

you now have the sources patched and ready to build in ~/<where you put your build>/build/linux-2.6.16.
with that you should be able tu build any modules.

Not sure if this is any easier that the other stuff ... but it's an alternative.

[InSearchOf]

make kernel_prepare will perform make kernel_get

So you can skip step 3 :-)

Late

[Capn_Fish]

1)install pdaxrom builder on a pc or virtual machine
2)follor the steps on note 101 upto when you start to actually build the romm (make all)
3)run make kernel_get
4)run make kernel_prepare

you now have the sources patched and ready to build in ~/<where you put your build>/build/linux-2.6.16.
with that you should be able tu build any modules.

Not sure if this is any easier that the other stuff ... but it's an alternative.

The sources at distro.ibiblio.../pdaxrom/src aren't patched? Does it matter? I'm trying to build the DM9601 module, and maybe packet-injection-patched hostap drivers, if it matters.

EDIT: Oh, and how hard is it to install the builder in a virtual machine and have networking support?

[louigi600]

The sources at distro.ibiblio.../pdaxrom/src aren't patched? Does it matter?

No ... they get patched with make kernel_prepare from the stuf in ~/pdaxrom_builder/trunk/local_patches/linux-2.6.16/arm/....

I'm trying to build the DM9601 module, and maybe packet-injection-patched hostap drivers, if it matters.

Once you have the whole kernel sources patched with the arm and pdaxrom patches you can do whatever you like: add other patches, change kernel setup, build kernel or build just modules. If you have no experience with this stuff read the README in the kernel sources.

EDIT: Oh, and how hard is it to install the builder in a virtual machine and have networking support?

It's a simple. I use vmware because xen is teased with the slackware non xen friendly Thread Safe Library so I can give you a quick overview for vmware:
install the vmware software (in this step you must decide what type of networking you are going to give to the virtual machines: (*)bridged or nat),
create a new virtual machine and give it decent resources (disk ram and cpu),
put the pdaxrom-builder.iso somewhere where the vmware virtual machine can see it,
set up the properties on the virtual machine so that it uses the iso image as CD image (not the physical dryve),
boot the virtual machine and setup the pdaxrom-builder to HD in the virtual machine,
setup the builder following note 101 (if I remember correctly).
There you are: 15 minutes work and you have the pdaxrom-builder working (understanding how it works is a different beast ... but you can bug the hell out of Adrian for that as he did the same to Sash in turn ;-) )

* Bridged is good if you can give your VM's real addresses belonging to the same address space of the host machine, nat is godd when you aonly have one address avalible on the network where the host is attached so the VM's get another IP address and get automatically natted (like masquerade) to the address of your host.

[Capn_Fish]

The sources at distro.ibiblio.../pdaxrom/src aren't patched? Does it matter?

No ... they get patched with make kernel_prepare from the stuf in ~/pdaxrom_builder/trunk/local_patches/linux-2.6.16/arm/....

I'm trying to build the DM9601 module, and maybe packet-injection-patched hostap drivers, if it matters.

Once you have the whole kernel sources patched with the arm and pdaxrom patches you can do whatever you like: add other patches, change kernel setup, build kernel or build just modules. If you have no experience with this stuff read the README in the kernel sources.

EDIT: Oh, and how hard is it to install the builder in a virtual machine and have networking support?

It's a simple. I use vmware because xen is teased with the slackware non xen friendly Thread Safe Library so I can give you a quick overview for vmware:
install the vmware software (in this step you must decide what type of networking you are going to give to the virtual machines: (*)bridged or nat),
create a new virtual machine and give it decent resources (disk ram and cpu),
put the pdaxrom-builder.iso somewhere where the vmware virtual machine can see it,
set up the properties on the virtual machine so that it uses the iso image as CD image (not the physical dryve),
boot the virtual machine and setup the pdaxrom-builder to HD in the virtual machine,
setup the builder following note 101 (if I remember correctly).
There you are: 15 minutes work and you have the pdaxrom-builder working (understanding how it works is a different beast ... but you can bug the hell out of Adrian for that as he did the same to Sash in turn ;-) )

* Bridged is good if you can give your VM's real addresses belonging to the same address space of the host machine, nat is godd when you aonly have one address avalible on the network where the host is attached so the VM's get another IP address and get automatically natted (like masquerade) to the address of your host.

What about doing this under Bochs or QEMU? I've had a little more experience with them (and they're more free).

EDIT: I'll just try it. If it fails, I can just try another and/or VMWarePlayer.

[Capn_Fish]

Now trying to follow the firections here (on a real HD):

http://www.pdaxrom.org/?q=node/93

But running setup does nothing. What's wrong? It's a SATA HD, if that matters.

Also, am I supposed to be able to boot from this partition? If so, what do I add to menu.lst?

Thanks.

[desertrat]

Now trying to follow the firections here (on a real HD):

http://www.pdaxrom.org/?q=node/93

But running setup does nothing. What's wrong? It's a SATA HD, if that matters.

Maybe pdaxrom doesn't have the drivers for SATA disks? Try "fdisk -l" and see if the HDD you want to use is listed.

[Capn_Fish]

Now trying to follow the firections here (on a real HD):

http://www.pdaxrom.org/?q=node/93

But running setup does nothing. What's wrong? It's a SATA HD, if that matters.

Maybe pdaxrom doesn't have the drivers for SATA disks? Try "fdisk -l" and see if the HDD you want to use is listed.

Yeah, it's there, and it shows up in /dev. The setup script implies that it supports SATA drives (it looks for sd* as well as hd* AFAICT).

EDIT: Rebooted and tried it without starting X, and it works. Stay tuned for the next problem!

[Capn_Fish]

OK, I finally got the setup to wrk, but now when I try to do the

CODE

make virtual-xchain_install

it fails to connect to the server. I used wget to DL the GCC source, but then it fails saying there is no room to decompress the source ("no space left on device").

Also, the partition that I specified in the "setup" isn't mounted, so I mounted it on /mnt/hd.

What am I doing wrong now?