From: "Muruga Ganapathy" <gmuruga@gdatech•com>
To: David Hawkins <dwh@ovro•caltech.edu>,
Eric Heim <sheldoninstruments@yahoo•com>,
linuxppc-embedded@ozlabs•org
Subject: Re: Windows boot recognition
Date: Tue, 3 Oct 2006 18:12:16 -0700 [thread overview]
Message-ID: <200610040112.k941CG112451@sierra.gdatech.com> (raw)
You may need to configure the board in PCI agent mode so that it can
respond to the PCI configuration cycles. By fefault, it might come
in master mode ( wherein it generates the PCI cycles and configures
other devices in its PCI bus)
It should be a hardware configuration option. So you should see a
jumper on the board or you may need to mount/unmount a resistor.
Pl check the hardware user manual.
Thanks
G.Muruganandam
> 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
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
*************************************************************
GDA Technologies, Inc.
1010 Rincon Circle
San Jose CA, 95131
Phone (408) 432-3090
Fax (408) 432-3091
Accelerate Your Innovation
**************************************************************
=====
This message contains information from GDA Technologies Inc and
affiliates, and is intended for the sole use of the individual and
entity to whom it is addressed. It may contain information, including
any attachments, that is privileged, confidential and exempt from
disclosure under applicable law. If you are not the intended
addressee, nor authorized to receive for the intended addressee, you
are hereby notified that you may not use, copy, disclose or distribute
to anyone the message or any information contained in the message. If
you have received this electronic transmission in error, please notify
the sender immediately by a "reply to sender only" message and destroy
all electronic and hard copies of the communication, including
attachments.
====
next reply other threads:[~2006-10-04 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 1:12 Muruga Ganapathy [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-03 22:15 Windows boot recognition Eric Heim
2006-10-03 23:18 ` David Hawkins
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=200610040112.k941CG112451@sierra.gdatech.com \
--to=gmuruga@gdatech$(echo .)com \
--cc=dwh@ovro$(echo .)caltech.edu \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=sheldoninstruments@yahoo$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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