From: David Hawkins <dwh@ovro.caltech.edu>
To: Eric Heim <sheldoninstruments@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Windows boot recognition
Date: Tue, 03 Oct 2006 16:18:57 -0700 [thread overview]
Message-ID: <4522EFE1.7000905@ovro.caltech.edu> (raw)
In-Reply-To: <20061003221526.59074.qmail@web37813.mail.mud.yahoo.com>
Hi Tim,
> I am trying to develop a windows driver for the MPC8349MDS board but
> Windows does not seem to acknowledge the existence of the board in the
> pci slot. The device manager does not see the board and no resources
> are allocated on boot.
If no resources are allocated on boot, then it indicates the BIOS
has not found the board. Have you booted this same machine under
Linux? If not, grab a Knoppix or Ubuntu CD and boot the machine
and see if lspci sees the board.
> Running Linux as my OS works perfectly. I have
> tried both Windows 2000 and XP on two different machines. Any ideas?
Under Windows I've used a tool called PCI tree to find
PCI resources of boards, it'll even let you manipulate
config space registers (much like setpci can under Linux).
Try running that tool to see if the board is setup
correctly by the BIOS.
If your Windows and Linux development machines are different,
then you may just be fighting with hardware. So first confirm
that the BIOS is finding the board.
Also check for hardware differences between the development
machines; eg. 33MHz or 66MHz, 32-bit or 64-bit PCI.
Dave
next prev parent reply other threads:[~2006-10-03 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 22:15 Windows boot recognition Eric Heim
2006-10-03 23:18 ` David Hawkins [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-04 1:12 Muruga Ganapathy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4522EFE1.7000905@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sheldoninstruments@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).