Re: [coreboot] SeaBIOS and USB UHCI keyboard support

[Mansoor]

Hi kevin,

Today I tested SeaBIOS USB support in my board. Unfortunately it didn't work

I connected a Dell keyboard.
Here is the error log

Starting SeaBIOS (version pre-0.4.3-20091009_174432-localhost.localdomain)

init usb
UHCI init on dev 00:1d.0 (io=f000)
ebda moved from 9f400 to 9f000
config_usb: 0x000fdf80 1
uhci_control 7000000
Timeout on wait_qh 0x0009fff0

Please let me know if you any other information

Regards
Mansoor

-----Original Message-----
From: Mansoor [mailto:[e-mail]] 
Sent: Wednesday, September 30, 2009 12:31 PM
To: 'Kevin O'Connor'; 'Stefan Reinauer'
Cc: 'coreboot'
Subject: RE: [coreboot] SeaBIOS and USB UHCI keyboard support

Its really a great news!!!. I will test this on my hardware (Intel Atom
(Silverthorne) & SCH US15W (Poulsbo) chipset)

A dumb question here... 
Why SeaBIOS have constrains? 
Can't we elaborate SeaBIOS as a driver part of coreboot? I mean a legacy
BIOS interrupts part(with constrains) + a driver section (includes support
for various drivers like USB keyboard USB mouse USB CDROM Hard disk etc)
without any constrains so that we can make use of current implementations
from Linux or other open source

Do you have any plan to support USB CD-ROM ?

-----Original Message-----

From: [e-mail] [mailto:[e-mail]]
On Behalf Of Kevin O'Connor
Sent: Wednesday, September 30, 2009 6:24 AM
To: Stefan Reinauer
Cc: coreboot
Subject: Re: [coreboot] SeaBIOS and USB UHCI keyboard support

Hi Stefan,

On Tue, Sep 29, 2009 at 04:47:04PM +0200, Stefan Reinauer wrote:
> Kevin O'Connor wrote:
> > The latest SeaBIOS git has preliminary support for USB keyboards.
> > I've tested this on qemu and on my epia-cn.
>
> Would it not make sense to pack USB keyboard functionality into our GSoC
> project instead, and use one common USB stack for all our projects?
> Especially since this renders usbrom completely unusable; no two USB
> stacks can operate the hw reliably at the same time.
>
> I'm a bit surprised by such action.

I'm sorry you were surprised.  I sent a note last month that I was
going to look at this.  I am truly sorry for the surprise and for any
disappointment.

SeaBIOS needs USB support in order to be usable on many platforms.  I
want SeaBIOS to be a "turn key" solution - that is, I want a vendor to
be able to boot up coreboot+seabios and say, "hey, this 'just works'".

I would prefer to pull in an external solution than implement a new
one.  Unfortunately, there isn't an external solution that works
today.

I looked closely at the libpayload code; I felt it would not work well
in the constrained environment that SeaBIOS runs in.  I believe
libpayload could be extended to support that constrained environment,
but I worry that would be an unnecessary burden on the other users of
libpayload (which aren't so constrained).

The support in SeaBIOS is currently 1029 lines of code - it is a
direct, no nonsense, just make it work implementation.
> Are you planning to add USB MSC
> support as well? Should we stop the OHCI efforts too and wait for your
> approach on that?

If someone steps forward with a solution that "just works", then I
will happily defer to that person.  Otherwise, I will continue to add
new features as I get time.

The next thing I am planning to look at is basic ohci keyboard
support, and then fleshing out the current keyboard support (eg,
auto-repeat, keyboard leds).

-Kevin

SeaBIOS and USB UHCI keyboard support

[Kevin O'Connor]

On Thu, Oct 29, 2009 at 12:42:28PM +0530, Mansoor wrote:
> Today I tested SeaBIOS USB support in my board. Unfortunately it didn't work

Hi Mansoor,

Thanks for testing.
> I connected a Dell keyboard.
> Here is the error log
>
> Starting SeaBIOS (version pre-0.4.3-20091009_174432-localhost.localdomain)
>
> init usb
> UHCI init on dev 00:1d.0 (io=f000)
> ebda moved from 9f400 to 9f000
> config_usb: 0x000fdf80 1
> uhci_control 7000000
> Timeout on wait_qh 0x0009fff0

I've added some more debugging info to the latest seabios git.  Can
you do a "git pull" and retry?  Also, can you send the output from
lscpi?

Thanks again.
-Kevin