Hello,
The xen.git development branch currently points to SeaBIOS rel-1.9.0, but
Roger has tripped over a build issue which is fixed by 3b8c5378dfe2 "build:
fix typo in buildversion.py".
Is there any plan for either a 1.9.1 or a 1.10.0 in the near future which
would include this, so I can roll forward to that?
Or if not a 1.9.1 release perhaps for now just a 1.9-stable branch could be
created?
No problem if not, we'll just track master for a bit until there is a
release.
Thanks,
Ian.
Hi, guys!
I wanna try to add NVMe support for SeaBIOS. But I have a problem: all addresses passed to NVMe ctrl (for example: queue addresses in ACQ and ASQ registers) are treated by controller as IO (not RAM).
Qemu 2.5.0: file exec.c: address_space_rw(): function memory_access_is_direct() returns false, but should be true. Am I missing smth, or it's special behaviour of SeaBios?
Have a nice day!
Best Regards,
Vladislav.
On Wed, Jan 27, 2016 at 08:05:38PM +0000, Eli Duttman wrote:
> Nothing has come my way, regarding my initial query. I'd appreciate a response, even if it is in the negative.
>
>
> I'm sorry my skills rate to be of zero help with the project. I can read a little C and dabbled with x86 assembler years ago. Nothing of consequence there.
>
>
> I'm an IBM mainframe CICS system programmer, with over 40 years of experience. If, by some chance, solid mainframe assembler and decent COBOL skills can be of use, I'd be delighted to pitch in.
>
> ________________________________
> From: Eli Duttman <eduttman(a)hotmail.com>
> Sent: Sunday, January 17, 2016 2:00 PM
> To: seabios(a)seabios.org
> Subject: Very Old Machines
>
> SeaBIOS seems to be a possibility for the ancient ISA bus machine
> reactivation project I have begun. What's currently in ROM lacks
> INT 13H extension support and is not Y2K compliant. When last used
> in the early 2000s, entering a 2nnn year seemed to be OK. An EEPROM
> is not present and any "load" would have to burned into 1 or more
> EPROMs.
>
> TIA, for any replies.
I'm not sure I understand what your question is.
The SeaBIOS code should run on any machine with a 386 or later.
However, machines have specific initialization sequences (such as
configuring the memory controller) and SeaBIOS does not implement that
at all - that is the role of the coreboot project. Given the age of
the machines you are working with, I suspect it will be very difficult
to figure out the low level details of the machine initialization.
-Kevin
Nothing has come my way, regarding my initial query. I'd appreciate a response, even if it is in the negative.
I'm sorry my skills rate to be of zero help with the project. I can read a little C and dabbled with x86 assembler years ago. Nothing of consequence there.
I'm an IBM mainframe CICS system programmer, with over 40 years of experience. If, by some chance, solid mainframe assembler and decent COBOL skills can be of use, I'd be delighted to pitch in.
Eli D.
________________________________
From: Eli Duttman <eduttman(a)hotmail.com>
Sent: Sunday, January 17, 2016 2:00 PM
To: seabios(a)seabios.org
Subject: Very Old Machines
SeaBIOS seems to be a possibility for the ancient ISA bus machine reactivation project I have begun. What's currently in ROM lacks INT 13H extension support and is not Y2K compliant. When last used in the early 2000s, entering a 2nnn year seemed to be OK. An EEPROM is not present and any "load" would have to burned into 1 or more EPROMs.
TIA, for any replies.
Eli D.
Hello Kevin,
I am trying to use the sdcard support in SeaBIOS.
It is working but the performance is far from optimal. As far as I was able to see this is because the current support is polling only.
Do you know if there are plans to make dma versions of the code available?
Best regards,
Wim Vervoorn
On Sat, Jan 23, 2016 at 12:24:38AM +0000, Bob Moore wrote:
> Hi,
>
> I'm new to qemu/seabios and am in the process of developing an
> option rom for a pcie device. I want to use seabios as a driver for
> debugging this code. I see documentation that says I can put my
> option rom into a file with name of the form pciVVVV,DDDD.rom to
> contain my compiled/linked code that will be used when the device
> having that VendorID/DeviceId is processed in init_pcirom(). The
> lookup_hardcode() call looks for this file on a list via
> romfile_find(). The list looks to be populated from FW_CFG_FILE_DIR
> but I can't seem to find where the entries on this list actually
> come from. Is there a specific directory in the qemu project that
> is configured to contain these entries? Or maybe these are just
> configured in a file someplace?
>
> Any help would be greatly appreciated.
As discussed offline, it's possible to use the qemu command line
-option-rom option. Alternatively, one can place the rom in fwcfg
directly via the -fw_cfg command line option. If you're writing qemu
code the fw_cfg_add_file() function is also available.
[...]
> HGST E-mail Confidentiality Notice & Disclaimer:
> This e-mail and any files transmitted with it may contain confidential or legally privileged information of HGST and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. If you have received this e-mail in error, please notify the sender immediately and delete the e-mail in its entirety from your system.
This email was sent to a public email list.
-Kevin