[PATCH] basic realmode handlers for int 0x10 and int 0x16

[Myles Watson]

My Jmicron SATA card writes the name of the hard drive to the screen.
This redirects that output to the console and implements a basic
keyboard stub.

Signed-off-by: Myles Watson

It makes the image a little bit larger (512 bytes after compression),
so I'm wondering if I should wrap it in a Kconfig option.  It doesn't
seem worth the mess in the code for such a little bit of space.

Thanks,
Myles

[Patrick Georgi]

Am 08.09.2010 01:38, schrieb Myles Watson:
> My Jmicron SATA card writes the name of the hard drive to the screen.
> This redirects that output to the console and implements a basic
> keyboard stub.
>
> Signed-off-by: Myles Watson

Acked-by: Patrick Georgi
> It makes the image a little bit larger (512 bytes after compression),
> so I'm wondering if I should wrap it in a Kconfig option.  It doesn't
> seem worth the mess in the code for such a little bit of space.

Looks good, and 512b compressed isn't worth the trouble imho.

Patrick

[PATCH] basic realmode handlers for int 0x10 and int 0x16

[Myles Watson]

On Thu, Sep 9, 2010 at 2:35 AM, Patrick Georgi  wrote:
> Am 08.09.2010 01:38, schrieb Myles Watson:
> > My Jmicron SATA card writes the name of the hard drive to the screen.
> > This redirects that output to the console and implements a basic
> > keyboard stub.
> >
> > Signed-off-by: Myles Watson
>
> Acked-by: Patrick Georgi
> > It makes the image a little bit larger (512 bytes after compression),
> > so I'm wondering if I should wrap it in a Kconfig option.  It doesn't
> > seem worth the mess in the code for such a little bit of space.
>
> Looks good, and 512b compressed isn't worth the trouble imho.

Great.

Rev 5793.

Thanks,
Myles