Hi,
> Virtio 1.0 block devices (virtio-blk/virtio-scsi) use a 64-bit BAR
> unusable by SeaBIOS if mapped over 4G space, preventing the system
> to boot.
Not needed, works fine in master (see commit
0e21548b15e25e010c362ea13d170c61a3fcc899).
Is not a clean cherry-pick for 1.9-stable though, so
On Mon, Sep 05, 2016 at 02:36:01PM -0400, Kevin O'Connor wrote:
> There were several keys not mapped in the keyboard scancode to
> "keycode" mapping functions. This series adds in a number of
> additional keyboard mappings. I used the Phoenix "System BIOS for IBM
> PC/XT/AT Computers and Compatib
On Mon, Sep 12, 2016 at 10:01:18AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > Virtio 1.0 block devices (virtio-blk/virtio-scsi) use a 64-bit BAR
> > unusable by SeaBIOS if mapped over 4G space, preventing the system
> > to boot.
>
> Not needed, works fine in master (see commit
> 0e21548b15e25e010c
Hi,
> > AFAIK latest seabios already supports DMA.
> > It's easy to add more config options for seabios
> > if you are so inclined.
>
> Yes, I tried that, the fw_cfg overhead in SeaBios/linuxboot optrom is
> already not a big issue for us. However, there are still some other
> code in SeaBIOS n
> > So, maybe it is time to plan a 1.10 release? There are also a number of
> > other improvements and cleanups in the master branch. Kevin?
>
> Makes sense. Freeze at end of month and release mid-October?
Looks good to me.
cheers,
Gerd
___
Sea
Move checking for release and extended scancodes to the top of
__process_key().
Signed-off-by: Kevin O'Connor
---
src/kbd.c | 70 +++
1 file changed, 30 insertions(+), 40 deletions(-)
diff --git a/src/kbd.c b/src/kbd.c
index 5945e99..3
Gerd Hoffmann wrote:
> * Initializing all pci devices (placing bars in address space and
>programming them) can probably be skipped and left to the linux
>kernel to handle.
When the coreboot project started out, in 1999, that turned out not
to be the case. I don't know if the situation ha