CODY:
My apologies. I didn’t understand that you are writing a BIOS. The
Linux part I mentioned refers to a product called LinuxBIOS, not the
Linux kernel itself, but it will also not help you.
In my opinion, you are down to RE here for your answers.
Unfortunately, to have any shot at all of following what ACPI does and
how it interacts with windows, you essentially must have a hardware
debugger, as SMM tends to be involved and it is not possible to trace
that with WinDbg.
MM
>> xxxxx@intel.com 2006-07-19 21:16 >>>
Hi, MM
Thanks for your information. I am afraid I haven’t stated my question
clearly enough. ![:slight_smile: :slight_smile:](/images/emoji/twitter/slight_smile.png?v=12)
I have access to bios’s source code ‘cause I myself is developing
bioses
so I know well how bios allocated resources. What puzzles me most is
how
windows handles it and certainly I have no access to windows’ source
code.
I have read part of linux kernel’s earlier source code and seems to me
it didn’t do any thing of reallocating resources or alike.
Best regards,
Cody
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Wednesday, July 19, 2006 8:24 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Windows OS Resource Allocation question
CODY:
Another resource is the source code for LinuxBIOS. It also shows, in
gory detail, the code for it’s implementation of INT 15, and
configuring
the bridges for a number of platforms that, assuming you are
considering
x86 or x64, should be fairly useful (although, last I checked, the x64
architecture was not complete, I think). If you have access to some
of
the more recent Intel Pentium embedded platforms, some of these come
with complete source code for a very excellent and complete BIOS. To
really see what is going on you need something like an ECM-50 to step
through from BIOS to logon. Tall order.
MM
>> xxxxx@mail.ru 2006-07-19 08:08 >>>
xxxxx@intel.com wrote:
Hi, all
I have just come across an article on MSDN saying that bios should
only allocate resource for IPL(Initial Program Load, i.e. devices
vital
to boot) devices and let windows do resource allocation to BUS devices
as much as possible because windows usually have better knowledge and
capability to do that.
Much contrary to that, modern bios thoroughly allocate resources to
each device it enumerate during POST and leave basically no space for
windows. I am curious to know if windows (the current version such as
Xp
or 2003) owns this capability to dynamically enumerate bus devices and
assign resources to them. If bios has made some wrong resouce
allocation
to devices such as overlap ranges, will windows proactively check and
correct it? Seems to me that they didn’t do anything right now.
Can anyone help to explain it? Thanks!
Best regards,
Cody
Hi, I think that Ms does that job (acpi.sys).
Some useful resources could be found here(http://acpi.info/) and just
an
example of configuring bridges(S & N) it was very interesting to read
(PC87550 PCI System Controller, it’s a National Semiconductor).
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer