What i did about Intel LinuxBIOS support 1. change ICH5 to ICH5R in v1. 2. move E7501 and ICH5R from V1 and V2.
For SB, documentation should be enough. For NB, I guess there is some undocumented info, and you may talk to intel directly or hack it out.
YH
-----Original Message----- From: Steven J. Magnani [mailto:steve@digidescorp.com] Sent: Friday, May 27, 2005 10:22 AM To: YhLu; linuxbios@openbios.org Subject: RE: [LinuxBIOS] Intel E7501 Northbridge head-scratching
Maybe change to use AMD or other platform, or even PowerPC.
The architecture is fixed. I either have to find a way to make LinuxBIOS work with it, or switch to something else. Which comes back to my original question...is there any more information available on the undocumented things the LinuxBIOS E7501 code does? Does the LinuxBIOS community support this code, or recommend against using it?
Steve
On Fri, 27 May 2005, YhLu wrote:
For NB, I guess there is some undocumented info, and you may talk to intel directly or hack it out.
and we can be pretty sure, based on Intel's comments w.r.t LinuxBIOS, that they will decline to help.
ron
Any one had any time to look at the EPIA-M code? Or is it still broken? -Adam
On Mon, 30 May 2005, Adam Talbot wrote:
Any one had any time to look at the EPIA-M code? Or is it still broken?
give us time, we're wrapping up epia now.
ron
On Tue, May 31, 2005 at 02:26:09AM +0000, Adam Talbot wrote:
Any one had any time to look at the EPIA-M code? Or is it still broken?
I'm interested in this too; I've hacked up a checkout from arch so it actually compiles for epia-m now, but I'm waiting for my BIOS Saviour to arrive before I can test it. It sounds like there are private trees floating around that have at least some extra work done on them though?
J.
Jonathan I have a prom flasher and am more then willing to test the code. If you would tar/gzip your tree and send it to me I will compile it for my EPIA-MII and test it for you. The worst that could happen is the system does not boot at all, that why I bought the prom flasher in the first place. :-) Adam
----- Original Message ----- From: "Jonathan McDowell" noodles@earth.li To: linuxbios@openbios.org Sent: Saturday, June 04, 2005 3:45 AM Subject: Re: [LinuxBIOS] EPIA-M status
On Tue, May 31, 2005 at 02:26:09AM +0000, Adam Talbot wrote:
Any one had any time to look at the EPIA-M code? Or is it still broken?
I'm interested in this too; I've hacked up a checkout from arch so it actually compiles for epia-m now, but I'm waiting for my BIOS Saviour to arrive before I can test it. It sounds like there are private trees floating around that have at least some extra work done on them though?
J.
-- Revd. Jonathan McDowell, ULC | Even the Evening Herald slags me off.
LinuxBIOS mailing list LinuxBIOS@openbios.org http://www.openbios.org/mailman/listinfo/linuxbios
On Sat, Jun 04, 2005 at 09:57:53AM -0700, Adam Talbot wrote:
I have a prom flasher and am more then willing to test the code. If you would tar/gzip your tree and send it to me I will compile it for my EPIA-MII and test it for you. The worst that could happen is the system does not boot at all, that why I bought the prom flasher in the first place. :-)
Heh. Well, I make absolutely no guarantees about this code other than "it compiles for me". It won't do VGA stuff and having had a further prod around there's a lot of cleanup that needs done around the vt1211 code. I've no way of running it or testing it until my kit arrives and I'm loathe to start making more changes until I've tested at least this lot to see if anything happens. :)
However, I've put what I've got up in an Arch repository.
tla register-archive noodles@earth.li--pie \ http://www.earth.li/~noodles/arch/noodles@earth.li--pie tla get noodles@earth.li--pie/freebios--epia-m--2.0 freebios2-epiam cd freebios2-epiam/targets ./buildtarget via/epia-m/Config.filo.lb cd via/epia-m/epia-m/ make
(You'll need a copy of filo.elf in the same directory as the freebios2-epiam subdirectory for the make to complete)
J.
Humm, so I am working on the EPIA-MII. Jonathan was kind enough to provide me with a compiling version of the source code. OK, I am stuck at this point. The code is compiled and flashed. Here is my console output. On the first reboot.
0
LinuxBIOS-1.1.8.0Fallback Sun Jun 5 22:31:42 PDT 2005 starting... vt8623 init starting vt8623 done
After the first reboot I have to set my connection speed to 57600 instead of 115200, and I get.
...`(...H....`(...H.
LinuxBIOS-1.1.8.0Normal Sun Jun 5 22:31:09 PDT 2005 starting...
Where do I turn up the debug so I can get a bit more info and perhaps track the problem?? -Adam
----- Original Message ----- From: "Jonathan McDowell" noodles@earth.li To: linuxbios@openbios.org Sent: Sunday, June 05, 2005 3:34 AM Subject: Re: [LinuxBIOS] EPIA-M status
On Sat, Jun 04, 2005 at 09:57:53AM -0700, Adam Talbot wrote:
I have a prom flasher and am more then willing to test the code. If you would tar/gzip your tree and send it to me I will compile it for my EPIA-MII and test it for you. The worst that could happen is the system does not boot at all, that why I bought the prom flasher in the first place. :-)
Heh. Well, I make absolutely no guarantees about this code other than "it compiles for me". It won't do VGA stuff and having had a further prod around there's a lot of cleanup that needs done around the vt1211 code. I've no way of running it or testing it until my kit arrives and I'm loathe to start making more changes until I've tested at least this lot to see if anything happens. :)
However, I've put what I've got up in an Arch repository.
tla register-archive noodles@earth.li--pie \ http://www.earth.li/~noodles/arch/noodles@earth.li--pie tla get noodles@earth.li--pie/freebios--epia-m--2.0 freebios2-epiam cd freebios2-epiam/targets ./buildtarget via/epia-m/Config.filo.lb cd via/epia-m/epia-m/ make
(You'll need a copy of filo.elf in the same directory as the freebios2-epiam subdirectory for the make to complete)
J.
-- 101 things you can't have too much of : 50 - Escalators.
LinuxBIOS mailing list LinuxBIOS@openbios.org http://www.openbios.org/mailman/listinfo/linuxbios
On Sun, Jun 05, 2005 at 10:42:02PM -0700, Adam Talbot wrote:
Humm, so I am working on the EPIA-MII. Jonathan was kind enough to provide me with a compiling version of the source code. OK, I am stuck at this point. The code is compiled and flashed. Here is my console output. On the first reboot.
0
LinuxBIOS-1.1.8.0Fallback Sun Jun 5 22:31:42 PDT 2005 starting... vt8623 init starting vt8623 done
After the first reboot I have to set my connection speed to 57600 instead of 115200, and I get.
...`(...H....`(...H.
LinuxBIOS-1.1.8.0Normal Sun Jun 5 22:31:09 PDT 2005 starting...
Oh cool. I was worried there wouldn't be any output at all which would be harder to diagnose. :)
Where do I turn up the debug so I can get a bit more info and perhaps track the problem??
Try adding:
uses DEFAULT_CONSOLE_LOGLEVEL uses MAXIMUM_CONSOLE_LOGLEVEL
to src/mainboard/via/epia-m/Options.lb just under "uses OBJCOPY"
and then:
option DEFAULT_CONSOLE_LOGLEVEL=9 option MAXIMUM_CONSOLE_LOGLEVEL=9
to targets/via/epia-m/Config.filo.lb just under "option HAVE_FALLBACK_BOOT=1"
You'll need to do the ./buildtarget again afterwards obviously.
J.
On Mon, Jun 06, 2005 at 10:17:19AM +0100, Jonathan McDowell wrote:
On Sun, Jun 05, 2005 at 10:42:02PM -0700, Adam Talbot wrote:
Where do I turn up the debug so I can get a bit more info and perhaps track the problem??
Try adding:
uses DEFAULT_CONSOLE_LOGLEVEL uses MAXIMUM_CONSOLE_LOGLEVEL
to src/mainboard/via/epia-m/Options.lb just under "uses OBJCOPY"
and then:
option DEFAULT_CONSOLE_LOGLEVEL=9 option MAXIMUM_CONSOLE_LOGLEVEL=9
to targets/via/epia-m/Config.filo.lb just under "option HAVE_FALLBACK_BOOT=1"
You'll need to do the ./buildtarget again afterwards obviously.
Also, I've just fixed up the config a bit more (and checked it into my arch tree) so the southbridge init stuff should actually get called - I don't think it was doing so before. Still looking at the right way to handle the vt1211 stuff.
J.
-Jonathan I grabbed the new tree. Here is the new output. (on the first boot) And that just keeps going, never stops. After the first reboot, I need to set my com settings to 57600 and just get "LinuxBIOS-1.1.8.0Normal Mon Jun 6 08:25:38 PDT 2005 starting..." and nothing else. Hope this helps in the debug process. -Adam
LinuxBIOS-1.1.8.0Normal Mon Jun 6 08:08:08 PDT 2005 starting... vt8623 init starting 00000000 is the north 1106 3123 e4 is the computed timing vt8623 done 00:06 11 23 31 06 00 30 22 00 00 00 06 00 08 00 00 10:08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00 20:00 00 00 00 00 00 00 00 00 00 00 00 06 11 01 aa 30:00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 40:00 18 88 80 82 44 00 00 18 99 88 80 82 44 00 00 50:c8 de cf 88 e0 07 00 00 e0 00 10 10 10 10 00 00 60:02 ff 00 30 e6 32 01 2e 59 2d 43 58 00 44 00 00 70:82 48 00 01 01 08 50 00 01 00 00 00 00 00 00 00 80:0f 65 00 00 f0 00 00 00 03 80 34 01 00 00 00 00 90:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0:02 c0 20 00 07 02 00 1f 04 00 00 00 2f 02 04 00 b0:00 00 00 00 80 00 00 00 68 00 00 00 00 00 00 00 c0:01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 d0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0:80 df 42 00 00 00 01 00 40 00 00 00 00 00 00 00 f0:00 00 00 00 00 00 11 13 00 00 00 00 00 00 00 00 Copying LinuxBIOS to ram. Jumping to LinuxBIOS. 0
LinuxBIOS-1.1.8.0Fallback Mon Jun 6 08:08:40 PDT 2005 starting... 0
LinuxBIOS-1.1.8.0Normal Mon Jun 6 08:08:08 PDT 2005 starting... vt8623 init starting 00000000 is the north 1106 3123 e4 is the computed timing vt8623 done 00:06 11 23 31 06 00 30 22 00 00 00 06 00 08 00 00 10:08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00 20:00 00 00 00 00 00 00 00 00 00 00 00 06 11 01 aa 30:00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 40:00 18 88 80 82 44 00 00 18 99 88 80 82 44 00 00 50:c8 de cf 88 e0 07 00 00 e0 00 10 10 10 10 00 00 60:02 ff 00 30 e6 32 01 2e 59 2d 43 58 00 44 00 00 70:82 48 00 01 01 08 50 00 01 00 00 00 00 00 00 00 80:0f 65 00 00 f0 00 00 00 03 80 34 01 00 00 00 00 90:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0:02 c0 20 00 07 02 00 1f 04 00 00 00 2f 02 04 00 b0:00 00 00 00 80 00 00 00 68 00 00 00 00 00 00 00 c0:01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 d0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0:80 df 42 00 00 00 01 00 40 00 00 00 00 00 00 00 f0:00 00 00 00 00 00 11 13 00 00 00 00 00 00 00 00 Copying LinuxBIOS to ram. Jumping to LinuxBIOS.
----- Original Message ----- From: "Jonathan McDowell" noodles@earth.li To: linuxbios@openbios.org Sent: Monday, June 06, 2005 2:17 AM Subject: Re: [LinuxBIOS] EPIA-M Almost there
On Sun, Jun 05, 2005 at 10:42:02PM -0700, Adam Talbot wrote:
Humm, so I am working on the EPIA-MII. Jonathan was kind enough to provide me with a compiling version of the source code. OK, I am stuck at this point. The code is compiled and flashed. Here is my console output. On the first reboot.
0
LinuxBIOS-1.1.8.0Fallback Sun Jun 5 22:31:42 PDT 2005 starting... vt8623 init starting vt8623 done
After the first reboot I have to set my connection speed to 57600 instead of 115200, and I get.
...`(...H....`(...H.
LinuxBIOS-1.1.8.0Normal Sun Jun 5 22:31:09 PDT 2005 starting...
Oh cool. I was worried there wouldn't be any output at all which would be harder to diagnose. :)
Where do I turn up the debug so I can get a bit more info and perhaps track the problem??
Try adding:
uses DEFAULT_CONSOLE_LOGLEVEL uses MAXIMUM_CONSOLE_LOGLEVEL
to src/mainboard/via/epia-m/Options.lb just under "uses OBJCOPY"
and then:
option DEFAULT_CONSOLE_LOGLEVEL=9 option MAXIMUM_CONSOLE_LOGLEVEL=9
to targets/via/epia-m/Config.filo.lb just under "option HAVE_FALLBACK_BOOT=1"
You'll need to do the ./buildtarget again afterwards obviously.
J.
-- OK, if we can't have a tour, can | .''`. Debian GNU/Linux Developer we at least have a look around? | : :' : Happy to accept PGP signed | `. `' or encrypted mail - RSA + | `- DSA keys on the keyservers.
LinuxBIOS mailing list LinuxBIOS@openbios.org http://www.openbios.org/mailman/listinfo/linuxbios
On Mon, Jun 06, 2005 at 08:31:34AM -0700, Adam Talbot wrote:
-Jonathan I grabbed the new tree. Here is the new output. (on the first boot) And that just keeps going, never stops. After the first reboot, I need to set my com settings to 57600 and just get "LinuxBIOS-1.1.8.0Normal Mon Jun 6 08:25:38 PDT 2005 starting..." and nothing else.
Hmmm. I wonder if it's the fact the CONFIG_CONSOLE_SERIAL8250 option doesn't appear to get set; in fact I don't see any console option set by default.
Try adding "uses CONFIG_CONSOLE_SERIAL8250" to src/mainboard/via/epia-m/Options.lb under the LOGLEVEL bits you added, and then "option CONFIG_CONSOLE_SERIAL8250=1" to targets/via/epia-m/Config.filo.lb and see if that gives you some more output?
J. - Wishing his BIOS Saviour would arrive soon so he can play himself.
Jonathan Well, that was cool... I have recompiled with the new options in place. Here is all my out put that I got, I just let minicom capture it. It was stuck in a dead loop, so I kill power after a bit. Still have the first boot at 115200 and all others need to be at 57600 issue. Hopes this helps in the debug. -Adam
On Mon, Jun 06, 2005 at 12:43:43PM -0700, Adam Talbot wrote:
Well, that was cool... I have recompiled with the new options in place. Here is all my out put that I got, I just let minicom capture it. It was stuck in a dead loop, so I kill power after a bit. Still have the first boot at 115200 and all others need to be at 57600 issue. Hopes this helps in the debug.
Slowly we seem to be making progress. :)
I /think/ the southbridge code needs some cleanup. It'll be a day or two before I have time to look properly, but if you shove
printk_debug("In VT8235 southbridge_enable\n");
in the southbridge_enable function in /src/southbridge/via/vt8235/vt8235.c that'll at least show if it ever gets that far. Don't worry if you don't have time though, as that whole area definitely looks like it needs work anyway.
The half baud rate problem is something I've seen mentioned before; something to do with the southbridge and various clocks settling down? I'll worry about it once other matters are sorted. ;)
J.
Jonathan New line of code in. Linuxbios bios recompiled... And yes, we are making it into the south bridge. Here is the new output. Adam
----- Original Message ----- From: "Jonathan McDowell" noodles@earth.li To: linuxbios@openbios.org Sent: Monday, June 06, 2005 3:23 PM Subject: Re: [LinuxBIOS] EPIA-M Almost there
On Mon, Jun 06, 2005 at 12:43:43PM -0700, Adam Talbot wrote:
Well, that was cool... I have recompiled with the new options in place. Here is all my out put that I got, I just let minicom capture it. It was stuck in a dead loop, so I kill power after a bit. Still have the first boot at 115200 and all others need to be at 57600 issue. Hopes this helps in the debug.
Slowly we seem to be making progress. :)
I /think/ the southbridge code needs some cleanup. It'll be a day or two before I have time to look properly, but if you shove
printk_debug("In VT8235 southbridge_enable\n");
in the southbridge_enable function in /src/southbridge/via/vt8235/vt8235.c that'll at least show if it ever gets that far. Don't worry if you don't have time though, as that whole area definitely looks like it needs work anyway.
The half baud rate problem is something I've seen mentioned before; something to do with the southbridge and various clocks settling down? I'll worry about it once other matters are sorted. ;)
J.
-- jid: noodles@jabber.earth.li noodles is the place to
LinuxBIOS mailing list LinuxBIOS@openbios.org http://www.openbios.org/mailman/listinfo/linuxbios
On Mon, Jun 06, 2005 at 07:47:56PM -0700, Adam Talbot wrote:
New line of code in. Linuxbios bios recompiled... And yes, we are making it into the south bridge.
Ok, I've updated the vt8235 stuff based on Josiah's EPIA work and checked it into my arch tree. As per usual, all it's passed is a compile test.
J.
we have fixes to epia. The commit via arch has failed. Once it is fixed, epia support is in.
ron
On Sun, Jun 05, 2005 at 12:49:14AM -0600, Ronald G. Minnich wrote:
we have fixes to epia. The commit via arch has failed. Once it is fixed, epia support is in.
This is plain EPIA support, isn't it (ie vt8601/vt8231)? Any closer to commit? Or is there even anywhere I can have a look at the diffs involved?
J.
On Sun, Jun 05, 2005 at 12:49:14AM -0600, Ronald G. Minnich wrote:
we have fixes to epia. The commit via arch has failed. Once it is fixed, epia support is in.
This is plain EPIA support, isn't it (ie vt8601/vt8231)? Any closer to commit? Or is there even anywhere I can have a look at the diffs involved?
Ollie or Josiah, please send jonathan a copy of your working tree until we can get arch fixed.
ron
* Ronald G. Minnich rminnich@lanl.gov [050607 05:33]:
This is plain EPIA support, isn't it (ie vt8601/vt8231)? Any closer to commit? Or is there even anywhere I can have a look at the diffs involved?
Ollie or Josiah, please send jonathan a copy of your working tree until we can get arch fixed.
Arch is perfectly operational. Maybe this should wait for SVN?
Stefan.
On Mon, 2005-06-06 at 23:25 +0100, Jonathan McDowell wrote:
On Sun, Jun 05, 2005 at 12:49:14AM -0600, Ronald G. Minnich wrote:
we have fixes to epia. The commit via arch has failed. Once it is fixed, epia support is in.
This is plain EPIA support, isn't it (ie vt8601/vt8231)? Any closer to commit? Or is there even anywhere I can have a look at the diffs involved?
J.
Attached is the diffs file generated by 'tla changes --diffs'. For your convenience, I've also put a gzipped tarball at http://klassified.info/freebios2--tla33-epia.tar.gz but the host apparently takes forever to sync disks so it may not show up there just yet.
On Tue, Jun 07, 2005 at 09:08:22AM -0600, Josiah England wrote:
Attached is the diffs file generated by 'tla changes --diffs'.
Great, thanks. Minor issue I found while using it as a basis for the EPIA-M stuff:
+static void ide_init(struct device *dev) +{
- struct southbridge_via_vt8231_config *conf;
- unsigned char enables;
- if (!conf->enable_native_ide) {
I think you want:
struct southbridge_via_vt8231_config *conf = dev->chip_info;
otherwise you're dereferencing an uninitialised pointer?
J.