Add initial support for i855gme. This is a work in progress and I
don't expect it to work on all boards, or even any besides mine. This
is based heavily on i855pm.
Signed off by Jon Dufresne <jon.dufresne(a)gmail.com>
The attached patch is a unified version of the current ports of the
i82801 series currently in LinuxBIOS. Since most of the ports are nearly
identical, I've taken for each file and chosen the cleanest or best
version of the code, then checked over the datasheets to *some* of the
series, including the aa, ba, ca, and db, to make sure that it would
work. I've also made some changes here and there, mostly cleanup and
clarification. The only things left to look at are the huge difference
between this version's lpc init and the i82801er's, finding a better way
to select which chip is present on the board, and gpl headers in all
files. Anyways, comments, suggestions, even flames are welcome ;)
Testing on other chips can be done at this point as well, this is tested
and working on one model, the i82801aa.
-Corey
Well, as there seems to be a lot of cleaning up going on lately, might
as well add this to the docket. The attached patch removes the Bitworks
IMS, as 1) there's no video support for it, 2) no one objected when this
was discussed previously, and 3) no one seems to have one, and they
aren't readily available. Any comments are welcome.
Signed-off-by: Corey Osgood <corey_osgood(a)verizon.net>
#80: serial console in grub2 works
---------------------------------+------------------------------------------
Reporter: oxygene | Owner: oxygene
Type: enhancement | Status: new
Priority: major | Milestone: Port GRUB2 to LinuxBIOS
Component: code | Version: v3
Keywords: | Dependencies:
Patchstatus: there is no patch |
---------------------------------+------------------------------------------
grub2 should be capable of using the serial console, just like lbv3 is
--
Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/80>
LinuxBIOS <http://www.linuxbios.org/>
Hi, all
I am developing the EFI payload for LB (see
http://code.google.com/soc/2007/coresystems/appinfo.html?csaid=83B941F46A422
F1A).
And I am unifying the resource management of LB and EFI. In more details, I
am parsing the LB table and converting it to the HOB structures of Tiano
EFI.
I described this idea several days ago.
(http://www.linuxbios.org/pipermail/linuxbios/2007-June/022340.html)
But there is a problem:
The Tiano EFI describes the system resources as types and attributes, such
as the following definition:
//*********************************************************
// EFI_RESOURCE_TYPE (define the resource type)
//*********************************************************
typedef UINT32 EFI_RESOURCE_TYPE;
#define EFI_RESOURCE_SYSTEM_MEMORY 0x00000000 (system memory resource)
#define EFI_RESOURCE_MEMORY_MAPPED_IO 0x00000001 (memory-mapped IO)
#define EFI_RESOURCE_IO 0x00000002 (Processor IO space)
#define EFI_RESOURCE_FIRMWARE_DEVICE 0x00000003 (Memory-mapped firmware
device)
#define EFI_RESOURCE_MEMORY_RESERVED 0x00000005 (Reserved memory address
space)
#define EFI_RESOURCE_IO_RESERVED 0x00000006 (Reserved IO address space)
//**************************************************************************
********
// EFI_RESOURCE_ATTRIBUTE_TYPE(define the resource attributes)
//**************************************************************************
********
typedef UINT32 EFI_RESOURCE_ATTRIBUTE_TYPE;
// These types can be ORed together as needed.
#define EFI_RESOURCE_ATTRIBUTE_PRESENT 0x00000001 (the memory region exists)
#define EFI_RESOURCE_ATTRIBUTE_INITIALIZED 0x00000002 (the memory region has
been initialized)
#define EFI_RESOURCE_ATTRIBUTE_TESTED 0x00000004 (the memory region has been
tested)
And there are similar definitions in the LB's /src/include/device/resourch.h
file.
But I can just find
IORESOURCE_MEM | IORESOURCE_CACHEABLE (system memory) resources types and
LB_MEM_RAM, LB_MEM_TABLE attributes in the LB tables.
So how to identify other resource types and attributes in LB?
Or the current LB implementation just describes these types and attributes,
I need to construct the rest resource types and attributes in the payload
itself as the exact requirement?
By the way, I built the LB with qemu emulation and just track qemu emulation
LB's source codes.
Thanks & Best regards,
Xiong Yi
Here's the chip_enable code for the ALI M1533 and the board_enable for
the Asus P5A, an ALI M1541+M1533 socket 7 motherboard.
It's quite nasty:
It does an SMBUS read/write to a yet unidentified device, i think it is
the superio, but i'm not sure.
The Asus P5A also seriously messes up pci-ids, there is nothing
dependable there, so people who want to use flashrom on this board
should use -m asus:p5a
but it works :)
This is a board i own myself and this has been tested successfully.
Luc Verhaegen.
#79: grub2 loads and executes as payload of the Qemu target
---------------------------------+------------------------------------------
Reporter: oxygene | Owner: oxygene
Type: defect | Status: new
Priority: major | Milestone: Port GRUB2 to LinuxBIOS
Component: code | Version: v3
Keywords: | Dependencies:
Patchstatus: there is no patch |
---------------------------------+------------------------------------------
For this issue to be done, grub2 should:
- be able to load modules that are brought in via grub-mkimage
- be able to use the LinuxBIOSv3 memory map
--
Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/79>
LinuxBIOS <http://www.linuxbios.org/>
#84: grub2 can boot linux from IDE disk
---------------------------------+------------------------------------------
Reporter: oxygene | Owner: oxygene
Type: enhancement | Status: new
Priority: major | Milestone: Port GRUB2 to LinuxBIOS
Component: code | Version: v3
Keywords: | Dependencies:
Patchstatus: there is no patch |
---------------------------------+------------------------------------------
Grub2 uses BIOS calls right now for access to disk. Replace this with a
driver that accesses ATA disks directly.
--
Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/84>
LinuxBIOS <http://www.linuxbios.org/>
Hey all. Following is a refresh of the LAR improvements that I posted
earlier. This revision includes fixes for comments from the mailing list,
bugs I discovered while integrating the code into buildROM, and last
(but not least), Doxygen style comments. I know some of this code got
ACKed last time I sent them out, but the messages were flying about
left and right, and I figured it would just be easier to re-send them all.
Also, not pictured here is the "remove-files" patch - I'll integrate it
with the add-stream.patch when I commit the code, but since it just
removes code, it isn't interesting to you guys.
Keep an eye out for the buildROM v3 enhancements, coming soon to a
mailing list near you. Following that, I have some plans for future
LAR work - including the manifest stuff we discussed earlier, as well
as possible replace/delete support in the LAR utility.
Enjoy,
Jordan
--
Jordan Crouse
Systems Software Development Engineer
Advanced Micro Devices, Inc.