Re: Re: Re: Building the custom firmware
Quote:
Originally posted by Oleg
Michael, I've not rebuild kernel, I've used the kernel & the modules supplied by ASUS. WRT54G kernel & modules can't be used directly - they have different ethernet interfaces, led drivers and possibly more. The closest kernel should be from the wap54 & wrt55. Asus also has the modules, which we can't recompile using the Linksys sources - the things related to parallel port (parport_splink), splink_led (it's pretty simple). And the main problem is the debugging of the newely build kernel.
BTW, I'm was able to build some modules to use with existing kernel using the wrt54g config (I've added the ext2, loop, nfs and the friends). I'm was able to mount nfs share.
I just looked in some of the kernel sources and some kernel boot outputs of the Linksys and the Asus Router.
The usb port is supported by the linksys modified kernel and they use the usb-ohci module for it..
The Ethernet ports are part of the broadcom chip, so they are also supported by the linksys sources.
Also broadcom only provides the binary kernel modules which should be ok. We can use those binary modules also in custom firmwares.
What is different is that Asus uses a other switch chip than linksys but this doesn't care, its outside of the linux stuff.
The Prt port is an Attansic at7601F, which they claim as IBM PC Compatible Printer Port (see http://www.attansic.com.tw/english/p...df/at7601f.pdf ).
So it should run with the standard parport module.
One of the things we need to find out to be able to compile the kernel correct is what modules are enabled in the ASUS kernel, Antiloop has posted this already. There we will get the messages which drivers were loaded. I will take a more detailed look myself, but my delivered WL500 was broken and i had to send it back.
I hope my replacement will be delivered soon.
As i said already Antiloop has posted the dmesg of the asus router in the openwrt thread, so we can see the the most of the modules the router uses.
What do you guys think of setting up a own Project on sourceforge ? We could use the provided cvs for storage of files and having a bugtracking aso. ?
We could also join Kaloz project in adopting the openwrt to the WL500.
I agree with you regarding the debug problem. But how do you debug a broken linux kernel on your pc ? Are you a real kernel hacker, i must admit that i can not do this. I can just try the things i compiled in and use them. If an error occures i just can upload a old working kernel.
Re: Re: Re: Re: Building the custom firmware
Quote:
Originally posted by zomk3
What do you guys think of setting up a own Project on sourceforge ? We could use the provided cvs for storage of files and having a bugtracking aso. ?
We could also join Kaloz project in adopting the openwrt to the WL500.
I agree with you regarding the debug problem. But how do you debug a broken linux kernel on your pc ? Are you a real kernel hacker, i must admit that i can not do this. I can just try the things i compiled in and use them. If an error occures i just can upload a old working kernel.
if in need of space chupa.nl has enough for now,
if you want to share bigger files send them through email to forum@chupa.nl, and i'll upload them at the site
i'm planning to create a upload page soon, so it can be uploaded to the site directly.
Re: Re: Re: Re: Re: Building the custom firmware
Quote:
Originally posted by Antiloop
if in need of space chupa.nl has enough for now,
if you want to share bigger files send them through email to forum@chupa.nl, and i'll upload them at the site
i'm planning to create a upload page soon, so it can be uploaded to the site directly.
I am not talking of binary files, i was thinking of the sources. cvs is a very usable tool for this. But if you'd like to set up a cvs or similar system ond chupa.nl that would be great. But think of maintenance and all the administrative stuff.
Re: Re: Re: Re: Building the custom firmware
Quote:
Originally posted by zomk3
The Ethernet ports are part of the broadcom chip, so they are also supported by the linksys sources.
....
So it should run with the standard parport module.
Once again, linksys (cybertan) wrt54g use different approach for the eth interfaces: they're using one physical ethernet port for both lan & wan and then drive two different connectors using the vlan tagging & built it switch chip. wl500g and all other similar things from dell, trendnet, buffalo and linksys wrt55 uses 2 physical enternet ports (this is reference design). BTW, there is not a big deal for compiling the kernel, which properly support ethernet ports (one of the linksys packages has original sources from broadcom with no vlan tagging dano by cybertan). But do you really need this new kernel right now? If you need additional features - compile these as modules.
As for parport - there are two modules loaded - parport & parport_splink, which uses parport. Don't know what parport_splink doing...
This is suffucient to start digging, but do we really need jffs on the flash? It's more resonable to use external USB disk for the purpose, saving the flash... WRT54G does not have usb port, so they decided to make the jffs partion.