From: "Tyler BIRD" <BIRDTY@uvsc.edu>
To: <jens_krueger@frm2.tu-muenchen.de>, <mj@ucw.cz>,
<linux-kernel@vger.kernel.org>
Subject: Re: PCI Subsystem
Date: Tue, 11 Dec 2001 09:13:13 -0700 [thread overview]
Message-ID: <sc15ce38.053@mail-smtp.uvsc.edu> (raw)
You probably could compile your drivers as modules and load them
with io ports on the command line. Then they would for sure use the right ports.
I don't know why you aren't receiving the correct io/ports from the PCI Config Address Space
does your driver take advantage of the the PCI standard
>>> Jens Krüger <jens_krueger@frm2.tu-muenchen.de> 12/11/01 05:26AM >>>
Hi,
I have a little problem with the PCI subsystem. I tried to use two cards of
the Meilhaus Co.. If I use the PCI access mode 'any' I don't get the right
I/O ports of the cards. Next I tried the access mode 'Direct' ( the output of
the lspci -v command is listed in the attached file lspci.direct) and the
access mode 'BIOS' (the output is stored in the file lspci.bios). There are
some little differences in the output, but all seems the same except the
output of the two Meilhaus cards. I have no idea for this behaviour. I tried
these cards under DOS and I got the same information as for the BIOS access
mode (the programm access the BIOS too), but in this mode all other cards
especially network card and USB don't work, so I can't use this mode. My
question: Is there any idea (or hack) to solve this problem?
With regards
Jens
--
Jens Krnger
Technische UniversitSt Mnnchen
ZBE FRM-II
Lichtenberg-Str. 1
D-85747 Garching
Tel: + 49 89 289 14 716
Fax: + 49 89 289 14 666
mailto:jens_krueger@frm2.tu-muenchen.de
http://www.frm2.tu-muenchen.de
next reply other threads:[~2001-12-11 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 16:13 Tyler BIRD [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-11 12:26 Jens Krüger
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=sc15ce38.053@mail-smtp.uvsc.edu \
--to=birdty@uvsc.edu \
--cc=jens_krueger@frm2.tu-muenchen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@ucw.cz \
/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
all inboxes | Powered by JetHome®