v2[PATCH] Initial support for the Thomson IP1000

[Joseph Smith]

Hello,
Here is a patch to add initial support for the Thomson IP1000. It is a
cousin to the RCA RM4100. More info on it can be found here:
http://www.settoplinux.org/index.php?title=Thomson_IP1000

Also attached is a coreboot bootlog with full debugging.

Signed-off-by: Joseph Smith

[Stefan Reinauer]

Joseph Smith wrote:
> Hello,
> Here is a patch to add initial support for the Thomson IP1000. It is a
> cousin to the RCA RM4100. More info on it can be found here:
> http://www.settoplinux.org/index.php?title=Thomson_IP1000
>
> Also attached is a coreboot bootlog with full debugging.
>
> Signed-off-by: Joseph Smith

One question: Are you seeing an error message similar to this one when
booting Linux?

PCI: Unable to handle 64-bit address space for bridge 0000:00:1c.0
PCI: Unable to handle 64-bit address space for bridge 0000:00:1c.4
PCI: Unable to handle 64-bit address space for bridge 0000:00:1c.5
PCI: Unable to handle 64-bit address space for bridge 0000:00:1e.0

I seem to get this on all recent 32bit systems I have touched when
booting with coreboot, but I could not figure out what it is, yet.

Stefan

[Joseph Smith]

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]]
> On Behalf Of Stefan Reinauer
> Sent: Friday, May 16, 2008 7:37 AM
> To: [e-mail]
> Cc: [e-mail]
> Subject: Re: [coreboot] v2[PATCH] Initial support for the Thomson IP1000
>
> Joseph Smith wrote:
> > Hello,
> > Here is a patch to add initial support for the Thomson IP1000. It is a
> > cousin to the RCA RM4100. More info on it can be found here:
> > http://www.settoplinux.org/index.php?title=Thomson_IP1000
> >
> > Also attached is a coreboot bootlog with full debugging.
> >
> > Signed-off-by: Joseph Smith
>
> One question: Are you seeing an error message similar to this one when
> booting Linux?
>
> PCI: Unable to handle 64-bit address space for bridge 0000:00:1c.0
> PCI: Unable to handle 64-bit address space for bridge 0000:00:1c.4
> PCI: Unable to handle 64-bit address space for bridge 0000:00:1c.5
> PCI: Unable to handle 64-bit address space for bridge 0000:00:1e.0
>
> I seem to get this on all recent 32bit systems I have touched when
> booting with coreboot, but I could not figure out what it is, yet.

Where are you seeing this? From the Linux kernel? It doesn't look familiar
to me. I'm not getting that on the RM4100 or IP1000. Does the board have
64-bit PCI slots?

[Stefan Reinauer]

Joseph Smith wrote:
> > One question: Are you seeing an error message similar to this one when
> > booting Linux?
> >
> > PCI: Unable to handle 64-bit address space for bridge 0000:00:1c.0
> > PCI: Unable to handle 64-bit address space for bridge 0000:00:1c.4
> > PCI: Unable to handle 64-bit address space for bridge 0000:00:1c.5
> > PCI: Unable to handle 64-bit address space for bridge 0000:00:1e.0
> >
> > I seem to get this on all recent 32bit systems I have touched when
> > booting with coreboot, but I could not figure out what it is, yet.
>
> Where are you seeing this? From the Linux kernel? It doesn't look familiar
> to me. I'm not getting that on the RM4100 or IP1000. Does the board have
> 64-bit PCI slots?

Yes, during Linux' PCI setup, when it encounters pci-to-pci or pcie bridges.

Stefan

[Joseph Smith]

On Fri, 16 May 2008 16:44:49 +0200, Stefan Reinauer 
wrote:
> Joseph Smith wrote:
> > > One question: Are you seeing an error message similar to this one when
> > > booting Linux?
> > >
> > > PCI: Unable to handle 64-bit address space for bridge 0000:00:1c.0
> > > PCI: Unable to handle 64-bit address space for bridge 0000:00:1c.4
> > > PCI: Unable to handle 64-bit address space for bridge 0000:00:1c.5
> > > PCI: Unable to handle 64-bit address space for bridge 0000:00:1e.0
> > >
> > > I seem to get this on all recent 32bit systems I have touched when
> > > booting with coreboot, but I could not figure out what it is, yet.
> >
> > Where are you seeing this? From the Linux kernel? It doesn't look
>
> familiar
> > to me. I'm not getting that on the RM4100 or IP1000. Does the board have
> > 64-bit PCI slots?

Hmm, not sure. I'm not getting that on the RM4100 or IP1000, booting FC7,
kernel 2.6.23.15-80.fc7.
Attached is a dmesg from the coreboot/IP1000.

v2[PATCH] Initial support for the Thomson IP1000 ACK?

[Joseph Smith]

On Thu, 15 May 2008 22:23:48 -0400, Joseph Smith 
wrote:
> Hello,
> Here is a patch to add initial support for the Thomson IP1000. It is a
> cousin to the RCA RM4100. More info on it can be found here:
> http://www.settoplinux.org/index.php?title=Thomson_IP1000
>
> Also attached is a coreboot bootlog with full debugging.
>
> Signed-off-by: Joseph Smith

Could I get an ACK on this new Target?

v2[PATCH] Initial support for the Thomson IP1000 ACK?

[Stefan Reinauer]

Joseph Smith wrote:
> On Thu, 15 May 2008 22:23:48 -0400, Joseph Smith 
> wrote:
> > Hello,
> > Here is a patch to add initial support for the Thomson IP1000. It is a
> > cousin to the RCA RM4100. More info on it can be found here:
> > http://www.settoplinux.org/index.php?title=Thomson_IP1000
> >
> > Also attached is a coreboot bootlog with full debugging.
> >
> > Signed-off-by: Joseph Smith
>
> Could I get an ACK on this new Target?

Acked-by: Stefan Reinauer

v2[PATCH] Initial support for the Thomson IP1000 ACK?

[Joseph Smith]

On Fri, 16 May 2008 17:30:59 +0200, Stefan Reinauer 
wrote:
> Joseph Smith wrote:
> > On Thu, 15 May 2008 22:23:48 -0400, Joseph Smith 
> > wrote:
> > > Hello,
> > > Here is a patch to add initial support for the Thomson IP1000. It is a
> > > cousin to the RCA RM4100. More info on it can be found here:
> > > http://www.settoplinux.org/index.php?title=Thomson_IP1000
> > >
> > > Also attached is a coreboot bootlog with full debugging.
> > >
> > > Signed-off-by: Joseph Smith
> >
> > Could I get an ACK on this new Target?
>
> Acked-by: Stefan Reinauer

Thanks r3328

v2[PATCH] Initial support for the Thomson IP1000 ACK?

[Joseph Smith]

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]]
> On Behalf Of Joseph Smith
> Sent: Friday, May 16, 2008 11:45 AM
> To: Stefan Reinauer
> Cc: [e-mail]
> Subject: Re: [coreboot] v2[PATCH] Initial support for the Thomson IP1000
> ACK?
>
> On Fri, 16 May 2008 17:30:59 +0200, Stefan Reinauer
>
> wrote:
> > Joseph Smith wrote:
> > > On Thu, 15 May 2008 22:23:48 -0400, Joseph Smith 
> > > wrote:
> > > > Hello,
> > > > Here is a patch to add initial support for the Thomson IP1000. It is a
> > > > cousin to the RCA RM4100. More info on it can be found here:
> > > > http://www.settoplinux.org/index.php?title=Thomson_IP1000
> > > >
> > > > Also attached is a coreboot bootlog with full debugging.
> > > >
> > > > Signed-off-by: Joseph Smith
> > >
> > > Could I get an ACK on this new Target?
> >
> > Acked-by: Stefan Reinauer
>
> Thanks r3328

Added to the Wiki.

Thanks,
Joseph Smith
Set-Top-Linux
www.settoplinux.org

[Uwe Hermann]

On Fri, May 16, 2008 at 10:49:48AM -0400, Joseph Smith wrote:
> ACPI Exception (utmutex-0263): AE_BAD_PARAMETER, Thread C37D2000 could not acquire Mutex [1] [20070126]

Looks scary, but probably harmless as you don't have ACPI.
> intel8x0_measure_ac97_clock: measured 50829 usecs
> intel8x0: clocking to 48000
> loop: module loaded
> IRQ handler type mismatch for IRQ 6
> current handler: uhci_hcd:usb3
>  [<c045abd0>] setup_irq+0x194/0x1ac
>  [<c41ef2de>] floppy_hardint+0x0/0xd8 [floppy]
>  [<c045ad82>] request_irq+0xc7/0xe5
>  [<c417d665>] init_module+0x536/0xe33 [floppy]
>  [<c061bfb6>] cond_resched+0x26/0x31
>  [<c044917d>] __link_module+0x0/0x10
>  [<c044917d>] __link_module+0x0/0x10
>  [<c044a80f>] sys_init_module+0x1361/0x14a5
>  [<c04e812c>] blk_init_queue+0x0/0x8
>  [<c040518a>] syscall_call+0x7/0xb
>  [<c0610000>] xfrm_send_policy_notify+0x35c/0x4fd
>  =======================
> floppy0: Unable to grab IRQ6 for the floppy driver

This doesn't look too good(?)

Not sure why this happens. You do disable floppy in Config.lb
via "device pnp 2e.0 off" (but maybe the stuff between that line
and the corresponding "end" has to be dropped? Not sure...

Can you post 'superiotool -dV' from BIOS and coreboot for comparison?

Also, your PIRQ table is the same as for RCA RM4100, is that really
the case? I.e. have you compared the getpir output of both?
> python[2050] general protection eip:a78d15 esp:bffec260 error:0

?

Uwe.

[Joseph Smith]

> -----Original Message-----
> From: coreboot-bounces+joe=[e-mail] [mailto:coreboot-
> bounces+joe=[e-mail]] On Behalf Of Uwe Hermann
> Sent: Friday, May 16, 2008 3:20 PM
> To: Joseph Smith
> Cc: Stefan Reinauer; [e-mail]
> Subject: Re: [coreboot] v2[PATCH] Initial support for the Thomson IP1000
>
> On Fri, May 16, 2008 at 10:49:48AM -0400, Joseph Smith wrote:
> > ACPI Exception (utmutex-0263): AE_BAD_PARAMETER, Thread C37D2000 could
>
> not acquire Mutex [1] [20070126]
>
> Looks scary, but probably harmless as you don't have ACPI.

Yes I think this is just because there is no ACPI. What is mutex anyways?
> > intel8x0_measure_ac97_clock: measured 50829 usecs
> > intel8x0: clocking to 48000
> > loop: module loaded
> > IRQ handler type mismatch for IRQ 6
> > current handler: uhci_hcd:usb3
> >  [<c045abd0>] setup_irq+0x194/0x1ac
> >  [<c41ef2de>] floppy_hardint+0x0/0xd8 [floppy]
> >  [<c045ad82>] request_irq+0xc7/0xe5
> >  [<c417d665>] init_module+0x536/0xe33 [floppy]
> >  [<c061bfb6>] cond_resched+0x26/0x31
> >  [<c044917d>] __link_module+0x0/0x10
> >  [<c044917d>] __link_module+0x0/0x10
> >  [<c044a80f>] sys_init_module+0x1361/0x14a5
> >  [<c04e812c>] blk_init_queue+0x0/0x8
> >  [<c040518a>] syscall_call+0x7/0xb
> >  [<c0610000>] xfrm_send_policy_notify+0x35c/0x4fd
> >  =======================
> > floppy0: Unable to grab IRQ6 for the floppy driver
>
> This doesn't look too good(?)
>
> Not sure why this happens. You do disable floppy in Config.lb
> via "device pnp 2e.0 off" (but maybe the stuff between that line
> and the corresponding "end" has to be dropped? Not sure...

Yeh this started when I updated the kernel there is no floppy and it is
disabled so not sure either... maybe a gpio setting?
> Can you post 'superiotool -dV' from BIOS and coreboot for comparison?

Sure, will do.
> Also, your PIRQ table is the same as for RCA RM4100, is that really
> the case? I.e. have you compared the getpir output of both?

It should be the same except as Corey said there is a PCI slot that needs to
be added. Linux was never able to run on this box until now, so I don't
really have any way to run getpir with the original bios.
> > python[2050] general protection eip:a78d15 esp:bffec260 error:0
>
> ?

Not sure about that one either.

Thanks,
Joseph Smith
Set-Top-Linux
www.settoplinux.org

[Uwe Hermann]

On Fri, May 16, 2008 at 03:49:39PM -0400, Joseph Smith wrote:
> > > IRQ handler type mismatch for IRQ 6
> > > current handler: uhci_hcd:usb3
> > >  [<c045abd0>] setup_irq+0x194/0x1ac
> > >  [<c41ef2de>] floppy_hardint+0x0/0xd8 [floppy]
> > >  [<c045ad82>] request_irq+0xc7/0xe5
> > >  [<c417d665>] init_module+0x536/0xe33 [floppy]
> > >  [<c061bfb6>] cond_resched+0x26/0x31
> > >  [<c044917d>] __link_module+0x0/0x10
> > >  [<c044917d>] __link_module+0x0/0x10
> > >  [<c044a80f>] sys_init_module+0x1361/0x14a5
> > >  [<c04e812c>] blk_init_queue+0x0/0x8
> > >  [<c040518a>] syscall_call+0x7/0xb
> > >  [<c0610000>] xfrm_send_policy_notify+0x35c/0x4fd
> > >  =======================
> > > floppy0: Unable to grab IRQ6 for the floppy driver
> >
> > This doesn't look too good(?)
> >
> > Not sure why this happens. You do disable floppy in Config.lb
> > via "device pnp 2e.0 off" (but maybe the stuff between that line
> > and the corresponding "end" has to be dropped? Not sure...
>
> Yeh this started when I updated the kernel there is no floppy and it is
> disabled so not sure either... maybe a gpio setting?
> > Can you post 'superiotool -dV' from BIOS and coreboot for comparison?
>
> Sure, will do.
> > Also, your PIRQ table is the same as for RCA RM4100, is that really
> > the case? I.e. have you compared the getpir output of both?
>
> It should be the same except as Corey said there is a PCI slot that needs to
> be added. Linux was never able to run on this box until now, so I don't
> really have any way to run getpir with the original bios.

Very nice! So for this box coreboot is not only an alternative to a
vendor BIOS, it's the _only_ way to run Linux? Make sure to mention
this in the wiki page.

Uwe.

[Joseph Smith]

> -----Original Message-----
> From: coreboot-bounces+joe=[e-mail] [mailto:coreboot-
> bounces+joe=[e-mail]] On Behalf Of Uwe Hermann
> Sent: Friday, May 16, 2008 4:50 PM
> To: Joseph Smith
> Cc: 'Stefan Reinauer'; [e-mail]
> Subject: Re: [coreboot] v2[PATCH] Initial support for the Thomson IP1000
>
> On Fri, May 16, 2008 at 03:49:39PM -0400, Joseph Smith wrote:
> > > > IRQ handler type mismatch for IRQ 6
> > > > current handler: uhci_hcd:usb3
> > > >  [<c045abd0>] setup_irq+0x194/0x1ac
> > > >  [<c41ef2de>] floppy_hardint+0x0/0xd8 [floppy]
> > > >  [<c045ad82>] request_irq+0xc7/0xe5
> > > >  [<c417d665>] init_module+0x536/0xe33 [floppy]
> > > >  [<c061bfb6>] cond_resched+0x26/0x31
> > > >  [<c044917d>] __link_module+0x0/0x10
> > > >  [<c044917d>] __link_module+0x0/0x10
> > > >  [<c044a80f>] sys_init_module+0x1361/0x14a5
> > > >  [<c04e812c>] blk_init_queue+0x0/0x8
> > > >  [<c040518a>] syscall_call+0x7/0xb
> > > >  [<c0610000>] xfrm_send_policy_notify+0x35c/0x4fd
> > > >  =======================
> > > > floppy0: Unable to grab IRQ6 for the floppy driver
> > >
> > > This doesn't look too good(?)
> > >
> > > Not sure why this happens. You do disable floppy in Config.lb
> > > via "device pnp 2e.0 off" (but maybe the stuff between that line
> > > and the corresponding "end" has to be dropped? Not sure...
> >
> > Yeh this started when I updated the kernel there is no floppy and it is
> > disabled so not sure either... maybe a gpio setting?
> > > Can you post 'superiotool -dV' from BIOS and coreboot for comparison?
> >
> > Sure, will do.
> > > Also, your PIRQ table is the same as for RCA RM4100, is that really
> > > the case? I.e. have you compared the getpir output of both?
> >
> > It should be the same except as Corey said there is a PCI slot that
>
> needs to
> > be added. Linux was never able to run on this box until now, so I don't
> > really have any way to run getpir with the original bios.
>
> Very nice! So for this box coreboot is not only an alternative to a
> vendor BIOS, it's the _only_ way to run Linux? Make sure to mention
> this in the wiki page.

Yes, the guys Set-Top-Linux are very excited about this! It originally comes
with a proprietary bios that only boots a windows CE image (nk.bin). So yes,
this is milestone for this box.

Thanks,
Joseph Smith
Set-Top-Linux
www.settoplinux.org

[Joseph Smith]

> Very nice! So for this box coreboot is not only an alternative to a
> vendor BIOS, it's the _only_ way to run Linux? Make sure to mention
> this in the wiki page.

Uwe, If you want a little history lesson on the RCA RM4100 & Thomson IP1000
than check out my about page:-)

http://www.settoplinux.org/index.php?title=Set-Top-Linux:About