SeaBIOS February 2012

seabios@seabios.org

27 participants
67 discussions

Re: [SeaBIOS] Time for a new release?
by Kevin O'Connor 15 Feb '12

15 Feb '12

On Thu, Feb 09, 2012 at 01:22:23PM +0100, Fred . wrote: > Lots of stuff have been happening lately (namely VGA and VBE related > stuff). Also some fixes. > > Perhaps it is time for a new release soon? It's a good question. I have some USB fixes I want to integrate before releasing. Does anyone else know of any issues that should be fixed before a release? -Kevin

6 8

Re: [SeaBIOS] SeaBIOS and Bochs?
by Paolo Bonzini 15 Feb '12

15 Feb '12

On 02/15/2012 11:21 AM, Fred . wrote: > How about 286 though? SeaBIOS has 32-bit code, so no way. Paolo

1 0

[PATCH] src/bootsplash.c: Fix displaying VGA bootsplash
by Gerhard Wiesinger 14 Feb '12

14 Feb '12

VGA bootsplash isn't displayed because video mode is set which clears the display. Video mode has already been set by the VGA BIOS. Signed-off-by: Gerhard Wiesinger <lists(a)wiesinger.com> --- src/bootsplash.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/src/bootsplash.c b/src/bootsplash.c index 76b72c1..8519bf4 100644 --- a/src/bootsplash.c +++ b/src/bootsplash.c @@ -38,12 +38,14 @@ void enable_vga_console(void) { dprintf(1, "Turning on vga text mode console\n"); +#ifdef SET_VGA_TEXT_MODE struct bregs br; /* Enable VGA text mode */ memset(&br, 0, sizeof(br)); br.ax = 0x0003; call16_int10(&br); +#endif // Write to screen. printf("SeaBIOS (version %s)\n\n", VERSION); -- 1.7.7.6

3 5

Re: [SeaBIOS] USB keyboard and mouse not detected
by Nils 14 Feb '12

14 Feb '12

Hi Kevin, You wrote: >> >Out of curiousity, if you disable ohci_free_pipe() (by adding a >> >"return" as the first statement of the function) does the keyboard >> >work long enough to get to the boot menu? >> >> I tested this and i couldn't get to the boot menu. > >Okay - that's weird. I wonder if this isn't just a matter of the >"free" code being incorrect. Can you send the log of the session with >ohci_free_pipe disabled? As i do not have a normal USB keyboard at the moment (last december i borrowed one) i have tested latest git again with my wireless Logitech keyboard/mouse combo. See attached log. If you prefer a log with a normal USB keyboard i will try to borrow it again. I have tried to debug this a little but had no succes yet. I tried to understand the OHCI spec. Am i right that you use the "LEGACY SUPPORT INTERFACE SPECIFICATION" via emulation interrupts and Legacy Support Registers 100h, 104h,(i/o address 60h) 108h(i/o address 60h) and 10Ch(i/o address 64h) ? I have "# CONFIG_PS2PORT is not set" because my target doesn't have a ps2 keyboard controller. I could not find the Legacy Support Register: HceControl (100h) being setup in SeaBIOS .(for emulating 60h + 64h) I think i found some code for that in Geode VSA that i suspect to be wrong, but i'm not sure yet. I also attached a lspci with coreboot/SeaBIOS + linux for reference.

2 1

Re: [SeaBIOS] [PATCH 3/5] vgabios: Claim VBE 3 support; minor VBE cleanups.
by Kevin O'Connor 14 Feb '12

14 Feb '12

On Tue, Feb 14, 2012 at 10:48:09AM +0100, Fred . wrote: > With the VBE 3.0 support claimed, perhaps it is time for a new release soon? I have a few more things on my list that I'd like to get through before starting a release process. (For example, some OHCI fixes.) It's probably worthwhile to start the discussion though. -Kevin

1 0

Relation between PCI device and Xenstore Device
by Daniel Castro 14 Feb '12

14 Feb '12

Hello All, I am writing some code to share some devices via the xenstore, yet I found a small problem. When I list the devices from the PCI I get the device id and the vendor id. On the xenstore I get the virtual-device, yet I have no apparent way to correctly map them, Do I need to enumerate the PCI devices, ask the size and then compare to xenstore so I can map them? but what if they have the same size? For example on my test VM I have to vbd 832 and 768 first is cdrom the second disk. On the pci I have this: Device Vendor 32902 4663 4115 184 22611 1 I am interested in 226611 that corresponds to XEN. Some light on this small issue? Thanks for the help. Daniel -- +-=====---------------------------+ | +---------------------------------+ | This space intentionally blank for notetaking. | | | Daniel Castro, | | | | Consultant/Programmer.| | | | U Andes | +-------------------------------------+

1 0

Re: [SeaBIOS] Problem with Debug lvl under XEN
by Ian Campbell 14 Feb '12

14 Feb '12

On Mon, 2012-02-13 at 23:21 +0900, Daniel Castro wrote: > Hello, > > I have encountered something a little strange, if I set up the debug > lvl to 3 or more Y will get a Triple VCPU fault. If I set it to 1 the > bios runs normally but I loose a lot of information that I need to > debug. Sometimes if I try to print char * variables regardless of the > debug level I still get the fault. > > Any ideas why? My guess is that there is a debug print at lvl>=3 which ends up dereferencing a NULL pointer in one of its arguments (probably a %s) and this leads to a page fault. This in turn leads to a double fault because SeaBIOS does not install a page fault handler and then a triple fault because it also does not install a double fault handler. Likewise when you are printing "char * variables regardless of the debug level". You could test this by adding an explicit check for null in the bit of bvprintf which handles %s, perhaps putc()ing "(null)" instead. > Thanks for the ideas/pointers/ anything! > > Daniel >

3 4

Re: [SeaBIOS] [PATCH 3/5] vgabios: Claim VBE 3 support; minor VBE cleanups.
by Fred . 14 Feb '12

14 Feb '12

With the VBE 3.0 support claimed, perhaps it is time for a new release soon? On Tue, Feb 14, 2012 at 2:35 AM, Kevin O'Connor <kevin(a)koconnor.net> wrote: > Claim support for VBE3 - that spec is actually more lenient for > required minimum support. > > Signed-off-by: Kevin O'Connor <kevin(a)koconnor.net> > --- > vgasrc/vbe.c | 18 ++++++++---------- > 1 files changed, 8 insertions(+), 10 deletions(-) > > diff --git a/vgasrc/vbe.c b/vgasrc/vbe.c > index 505cb61..852edbc 100644 > --- a/vgasrc/vbe.c > +++ b/vgasrc/vbe.c > @@ -11,7 +11,7 @@ > #include "bregs.h" // struct bregs > #include "vbe.h" // struct vbe_info > #include "util.h" // dprintf > -#include "biosvar.h" // get_global_set > +#include "biosvar.h" // GET_GLOBAL > #include "vgahw.h" // vgahw_set_mode > > u32 VBE_total_memory VAR16 = 256 * 1024; > @@ -37,7 +37,7 @@ vbe_104f00(struct bregs *regs) > > SET_FARVAR(seg, info->signature, VESA_SIGNATURE); > > - SET_FARVAR(seg, info->version, 0x0200); > + SET_FARVAR(seg, info->version, 0x0300); > > SET_FARVAR(seg, info->oem_string, > SEGOFF(get_global_seg(), (u32)VBE_OEM_STRING)); > @@ -47,7 +47,7 @@ vbe_104f00(struct bregs *regs) > u16 *destmode = (void*)info->reserved; > SET_FARVAR(seg, info->video_mode, SEGOFF(seg, (u32)destmode)); > > - /* Total memory (in 64 blocks) */ > + /* Total memory (in 64k blocks) */ > SET_FARVAR(seg, info->total_memory > , GET_GLOBAL(VBE_total_memory) / (64*1024)); > > @@ -77,7 +77,7 @@ vbe_104f01(struct bregs *regs) > struct vgamode_s *vmode_g = vgahw_find_mode(mode); > if (! vmode_g) { > dprintf(1, "VBE mode %x not found\n", mode); > - regs->ax = 0x0100; > + regs->ax = 0x014f; > return; > } > > @@ -88,10 +88,7 @@ vbe_104f01(struct bregs *regs) > VBE_MODE_ATTRIBUTE_GRAPHICS_MODE | > VBE_MODE_ATTRIBUTE_NOT_VGA_COMPATIBLE; > u32 framebuffer = GET_GLOBAL(VBE_framebuffer); > - int depth = GET_GLOBAL(vmode_g->depth); > - if (depth == 4) > - mode_attr |= VBE_MODE_ATTRIBUTE_TTY_BIOS_SUPPORT; > - else if (framebuffer) > + if (framebuffer) > mode_attr |= VBE_MODE_ATTRIBUTE_LINEAR_FRAME_BUFFER_MODE; > SET_FARVAR(seg, info->mode_attributes, mode_attr); > SET_FARVAR(seg, info->winA_attributes, > @@ -114,13 +111,14 @@ vbe_104f01(struct bregs *regs) > SET_FARVAR(seg, info->yres, height); > SET_FARVAR(seg, info->xcharsize, GET_GLOBAL(vmode_g->cwidth)); > SET_FARVAR(seg, info->ycharsize, GET_GLOBAL(vmode_g->cheight)); > + int depth = GET_GLOBAL(vmode_g->depth); > int planes = (depth == 4) ? 4 : 1; > SET_FARVAR(seg, info->planes, planes); > SET_FARVAR(seg, info->bits_per_pixel, depth); > SET_FARVAR(seg, info->banks, 1); > SET_FARVAR(seg, info->mem_model, GET_GLOBAL(vmode_g->memmodel)); > SET_FARVAR(seg, info->bank_size, 0); > - u32 pages = GET_GLOBAL(VBE_total_memory) / (height * linesize); > + u32 pages = GET_GLOBAL(VBE_total_memory) / ALIGN(height * linesize, 64*1024); > SET_FARVAR(seg, info->pages, (pages / planes) - 1); > SET_FARVAR(seg, info->reserved0, 1); > > @@ -259,7 +257,7 @@ vbe_104f05(struct bregs *regs) > regs->ax = 0x004f; > return; > fail: > - regs->ax = 0x0100; > + regs->ax = 0x014f; > } > > static void > -- > 1.7.6.5 > > > _______________________________________________ > SeaBIOS mailing list > SeaBIOS(a)seabios.org > http://www.seabios.org/mailman/listinfo/seabios

1 0

[PATCH 0/5] Some vgabios tweaks
by Kevin O'Connor 13 Feb '12

13 Feb '12

Some additional tweaks. The first patch impacts the main bios as well. -Kevin Kevin O'Connor (5): Direct compile 16bit C code instead of including via .S files. vgabios: Add version string to debug output. vgabios: Claim VBE 3 support; minor VBE cleanups. vgabios: Minor vgabios fixes. vgabios: Some tweaks to optimize stack space. Makefile | 62 +++++++++++++++----------- src/code16gcc.s | 1 + src/romlayout.S | 11 +---- tools/checkstack.py | 2 +- vgasrc/clext.c | 4 +- vgasrc/vbe.c | 20 ++++----- vgasrc/vgabios.c | 120 ++++++++++++++++++++------------------------------ vgasrc/vgabios.h | 8 +++- vgasrc/vgaentry.S | 10 +--- 9 files changed, 107 insertions(+), 131 deletions(-) create mode 100644 src/code16gcc.s -- 1.7.6.5

1 5

Re: [SeaBIOS] USB keyboard and mouse not detected
by Nils 13 Feb '12

13 Feb '12

>On Mon, Dec 26, 2011 at 10:31:35PM +0100, Nils wrote: >> With that patch: >> >> pmm_free 0x1f7b4a30 (detail=0x1f7b4a60) >> ohci_free_pipe 0x1f7b4aa0 >> signal_freelist control=97 >> signal_freelist2 control=87 >> WARNING - Timeout at ohci_waittick:275! >> pmm_free 0x1f7b4a90 (detail=0x1f7b4ac0) >> ohci_free_pipe 0x1f7b4b00 >> signal_freelist control=97 >> signal_freelist2 control=87 >> WARNING - Timeout at ohci_waittick:275! >> pmm_free 0x1f7b4af0 (detail=0x1f7b4b20) >> init serial >> Found 1 serial ports > >Out of curiousity, if you disable ohci_free_pipe() (by adding a >"return" as the first statement of the function) does the keyboard >work long enough to get to the boot menu? I tested this and i couldn't get to the boot menu. Thanks, Nils.

2 1

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SeaBIOS February 2012