Hello, How hard is it to port a chipset from version 1 to version 2? I have a Intel 82830 Northbridge (only V1) and I need to port it to V2. All the rest of my hardware is already listed in V2. Can somone point me in the right direction?
Thanks - Joe
Hello, How hard is it to port a chipset from version 1 to version 2? I have a Intel 82830 Northbridge (only V1) and I need to port it to V2. All the rest of my hardware is already listed in V2. Can somone point me in the right direction?
Thanks - Joe
-- linuxbios mailing list linuxbios@linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios
Hello, I wish to carry out the same thing but for the motherboard advantech/pcm-5823, he exist in v1 but not in v2, all the chip is already listed in V2 except the winbond W83977AF. Can someone point me in the right direction ?
Thanks by advance CCases
ccases@navista.fr wrote:
Hello, I wish to carry out the same thing but for the motherboard advantech/pcm-5823, he exist in v1 but not in v2, all the chip is already listed in V2 except the winbond W83977AF. Can someone point me in the right direction ?
If you already have the hardware to test with (bios savior or extra chips) try creating a target and using winbond w83977tf (ie just tell linuxbios that's what it is). From a quick look at the source, it doesn't seem there is anything that should block it from working. Even if it doesn't work, but everything else works, VGA and USB should still work, unless a failed superio causes it to hang, but again looking at the source it doesn't seem it should. You just won't have any serial or PS/2 ports until you do get it working.
-Corey
ccases@navista.fr wrote:
Hello, I wish to carry out the same thing but for the motherboard advantech/pcm-5823, he exist in v1 but not in v2, all the chip is already listed in V2 except the winbond W83977AF. Can someone point me in the right direction ?
If you already have the hardware to test with (bios savior or extra chips) try creating a target and using winbond w83977tf (ie just tell linuxbios that's what it is). From a quick look at the source, it doesn't seem there is anything that should block it from working. Even if it doesn't work, but everything else works, VGA and USB should still work, unless a failed superio causes it to hang, but again looking at the source it doesn't seem it should. You just won't have any serial or PS/2 ports until you do get it working.
-Corey
Yes I have a chip programmator. I don't understand if it's possible tu use the source of v1 en test it directly (on the web for the v1 it are noted like nonfunctional), or if I must modify the files to function with the v2 ? For me if the VGA, the USB, and the network (rtl8139c) work it's sufficient.
Thank's by advance for your help,
Ccases
Hi,
On Thu, Feb 22, 2007 at 09:43:50AM +0100, ccases@navista.fr wrote:
I wish to carry out the same thing but for the motherboard advantech/pcm-5823, he exist in v1 but not in v2, all the chip is already listed in V2 except the winbond W83977AF. Can someone point me in the right direction ?
If you already have the hardware to test with (bios savior or extra chips) try creating a target and using winbond w83977tf (ie just tell linuxbios that's what it is).
Yes, that should work. Both are very similar and the serial ports have the same logical device numbers so you should be fine.
From a quick look at the source, it doesn't seem there is anything that should block it from working. Even if it doesn't work, but everything else works, VGA and USB should still work, unless a failed superio causes it to hang, but again looking at the source it doesn't seem it should. You just won't have any serial or PS/2 ports until you do get it working.
-Corey
Yes I have a chip programmator. I don't understand if it's possible tu use the source of v1 en test it directly (on the web for the v1 it are noted like nonfunctional), or if I must modify the files to function with the v2
I recommend to try v1 first, just to verify that/if it works there, then you can concentrate on v2.
You cannot use the v1 code as is for v2, though. It must be ported. But the code is pretty small and porting should be doable.
For me if the VGA, the USB, and the network (rtl8139c) work it's sufficient.
First you should test whether the super I/O works, i.e. if you get serial output. That's esential for debugging.
Then you need to get the northbridge (RAM) working, then the southbridge (for peripheral devices, e.g. network, USB)...
Uwe.
Hi,
On Thu, Feb 22, 2007 at 09:43:50AM +0100, ccases@navista.fr wrote:
I wish to carry out the same thing but for the motherboard advantech/pcm-5823, he exist in v1 but not in v2, all the chip is already listed in V2 except the winbond W83977AF. Can someone point me in the right direction ?
If you already have the hardware to test with (bios savior or extra chips) try creating a target and using winbond w83977tf (ie just tell linuxbios that's what it is).
Yes, that should work. Both are very similar and the serial ports have the same logical device numbers so you should be fine.
From a quick look at the source, it doesn't seem there is anything that should block it from working. Even if it doesn't work, but everything else works, VGA and USB should
still
work, unless a failed superio causes it to hang, but again looking at the source it doesn't seem it should. You just won't have any serial
or
PS/2 ports until you do get it working.
-Corey
Yes I have a chip programmator. I don't understand if it's possible tu use the source of v1 en test it directly (on the web for the v1 it are noted like nonfunctional), or if I must modify the files to function with the v2
I recommend to try v1 first, just to verify that/if it works there, then you can concentrate on v2.
You cannot use the v1 code as is for v2, though. It must be ported. But the code is pretty small and porting should be doable.
For me if the VGA, the USB, and the network (rtl8139c) work it's sufficient.
First you should test whether the super I/O works, i.e. if you get serial output. That's esential for debugging.
Then you need to get the northbridge (RAM) working, then the southbridge (for peripheral devices, e.g. network, USB)...
Uwe.
http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org -- linuxbios mailing list linuxbios@linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios
ok thank's for your help, I try to test the V1 and I keep you informed,
regards
Ccases
I have test to compil the mainboard iei nova4899r, I have use buildtarguet for create config file and makefile, but if I tape a make on :
../LinuxBIOSv2/targets/iei/nova4899r/nova4899r/
I have an error :
... FAILOVER_IMAGE='0' /home/ccases/projet_bios/source_linuxBios/LinuxBIOSv2/src/mainboard/iei/nova4899r/failover.c -o failover.inc' make[1]: *** [failover.inc] Erreur 2 make[1]: Leaving directory `/home/ccases/projet_bios/source_linuxBios/LinuxBIOSv2/targets/iei/nova4899r/nova4899r/fallback' make: *** [fallback/linuxbios.rom] Erreur 1
I don't know why I have this problem. If anyone nows ?
thank's by advance
CCases
I have test to compil the mainboard iei nova4899r, I have use buildtarguet for create config file and makefile, but if I tape a make on :
../LinuxBIOSv2/targets/iei/nova4899r/nova4899r/
I have an error :
... FAILOVER_IMAGE='0' /home/ccases/projet_bios/source_linuxBios/LinuxBIOSv2/src/mainboard/iei/nova4899r/failover.c -o failover.inc' make[1]: *** [failover.inc] Erreur 2 make[1]: Leaving directory `/home/ccases/projet_bios/source_linuxBios/LinuxBIOSv2/targets/iei/nova4899r/nova4899r/fallback' make: *** [fallback/linuxbios.rom] Erreur 1
I don't know why I have this problem. If anyone nows ?
thank's by advance
CCases
-- linuxbios mailing list linuxbios@linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios
If I test an oser mainboard, I have this error :
... make[1]: *** [build_opt_tbl] Erreur 2 make[1]: Leaving directory `/home/ccases/LinuxBIOSv2/targets/tyan/s2735/s2735/normal' make: *** [normal/linuxbios.rom] Erreur 1
I d'ont know why. :(
CCases
Ok, I think I got it figured out. Attached is my config. Would someone mind taking a quick look to see if it looks good?? Feedback?
Thanks - Joe
Quoting joe@smittys.pointclark.net:
Hello, How hard is it to port a chipset from version 1 to version 2? I have a Intel 82830 Northbridge (only V1) and I need to port it to V2. All the rest of my hardware is already listed in V2. Can somone point me in the right direction?
Thanks - Joe
-- linuxbios mailing list linuxbios@linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios
joe@smittys.pointclark.net wrote:
Ok, I think I got it figured out. Attached is my config. Would someone mind taking a quick look to see if it looks good?? Feedback?
Thanks - Joe
Quoting joe@smittys.pointclark.net:
Hello, How hard is it to port a chipset from version 1 to version 2? I have a Intel 82830 Northbridge (only V1) and I need to port it to V2. All the rest of my hardware is already listed in V2. Can somone point me in the right direction?
I don't think your northbridge is going to work. 440bx afaik isn't working right now, so your quick hack (no offense) to 430 probably isn't going to work either (although it might). Make sure you've got some sort of system for getting the factory bios back if it fails (BIOS saviors are wonderful, if you can get one). Also, when sending things to the list, it's best if you whip off a patch, as described here: http://www.linuxbios.org/Development_Guidelines#Creating_Patches, it really helps to clarify where you've made changes and point out what you've done. LinuxBIOSv1 also has support for the 430tx, as you've already noted, and you'll find a lot of info on how things work there, if you understand assembly. Intel also has some datasheets for both the 430tx and hx, they're all available with a little clicking from here: http://www.intel.com/support/chipsets/sb/cs-009194.htm
I'm looking at some pictures of the rm4100 (you got me interested in it), and it doesn't look like there's even a serial port header, let alone a serial port. Do you have one on your board? That will be pretty much essential to debugging. As for your TV-Out, initializing it should be done by the onboard video BIOS, which you'll have to extract and use with a similar process to the one described here: http://www.linuxbios.org/FAQ#Testbios_.28vgabios.29_Faq
If you've got any other questions, please post back. I'm certainly no expert on linuxbios, but I'll try to help if I can, and if not, there are others around that probably can.
-Corey
Quoting Corey Osgood corey_osgood@verizon.net:
joe@smittys.pointclark.net wrote:
Ok, I think I got it figured out. Attached is my config. Would someone mind taking a quick look to see if it looks good?? Feedback?
Thanks - Joe
Quoting joe@smittys.pointclark.net:
Hello, How hard is it to port a chipset from version 1 to version 2? I have a Intel 82830 Northbridge (only V1) and I need to port it to V2. All the rest of my hardware is already listed in V2. Can somone point me in the right direction?
I don't think your northbridge is going to work. 440bx afaik isn't working right now, so your quick hack (no offense) to 430 probably isn't going to work either (although it might). Make sure you've got some sort of system for getting the factory bios back if it fails (BIOS saviors are wonderful, if you can get one). Also, when sending things to the list, it's best if you whip off a patch, as described here: http://www.linuxbios.org/Development_Guidelines#Creating_Patches, it really helps to clarify where you've made changes and point out what you've done. LinuxBIOSv1 also has support for the 430tx, as you've already noted, and you'll find a lot of info on how things work there, if you understand assembly. Intel also has some datasheets for both the 430tx and hx, they're all available with a little clicking from here: http://www.intel.com/support/chipsets/sb/cs-009194.htm
I'm looking at some pictures of the rm4100 (you got me interested in it), and it doesn't look like there's even a serial port header, let alone a serial port. Do you have one on your board? That will be pretty much essential to debugging. As for your TV-Out, initializing it should be done by the onboard video BIOS, which you'll have to extract and use with a similar process to the one described here: http://www.linuxbios.org/FAQ#Testbios_.28vgabios.29_Faq
If you've got any other questions, please post back. I'm certainly no expert on linuxbios, but I'll try to help if I can, and if not, there are others around that probably can.
-Corey
Thanks for the feedback Corey. As far as the tv-out, I don't think that is going to be possible to extract it. the rm4100 does not have a standard bios. It is a custom designed one for wince and it sucks. If you want to check out the project my website is:
http://www.smittys.pointclark.net/rm4100/index.php
There are alot of pics there. It does have a serial port you just have to use a TTL to Serial adapter, just like many cell phones etc. We are in much need of a better bios for Linux. That's why I am on a quest for Linuxbios. Anyone interested in helping would be greatly appreciated.
Thanks - Joe
Hi,
On Thu, Feb 22, 2007 at 07:55:12AM -0500, joe@smittys.pointclark.net wrote:
Thanks for the feedback Corey. As far as the tv-out, I don't think that is going to be possible to extract it. the rm4100 does not have a standard bios. It is a custom designed one for wince and it sucks. If you want to check out the project my website is:
This would indeed be an interesting project to get working.
Can you send an lspci output to the list, please?
Looking at the pictures, this is a standard PLCC BIOS chip, and it's socketed, so you can rip it out and replace it with another one (running LinuxBIOS if you get everything working).
The Super I/O is an SMSC LPCxxxxx (can't read the extact part number on the picture). Can you please post the part number? This shouldn't be too hard to get working.
Anyone interested in helping would be greatly appreciated.
We can help you on the list interactively if you're willing to test patches etc...
Do you have some spare PLCC chips you can use for LinuxBIOS development?
You already have a running Linux on the box, is this correct?
HTH, Uwe.