From: "Amelia De Vivo" <amelia@roma.quadrics.com>
To: <linuxppc-dev@lists.linuxppc.org>
Subject: Addressing PCI memory
Date: Tue, 15 May 2001 18:34:50 +0200 [thread overview]
Message-ID: <002f01c0dd5c$f64942e0$7a00000a@roma.quadrics.com> (raw)
Hi all, I'm trying to write a driver for a 64 bit PCI device. Something like
this works well under i386 Linux, but it doesn't work at all for Linux
2.2.15 by Yellow Dog:
struct pci_dev *dev = NULL;
dev = pci_find_device(vendor, device, dev);
pci_read_config_dword(dev, PCI_BASE_ADDRESS_0, &cards[0].addr0);
cards[0].vaddr = (void *) ioremap((cards[0].addr0 &
PCI_BASE_ADDRESS_MEM_MASK), cards[0].size);
writeb('A',(cards[0].vaddr)+0x1000);
I have a kernel panic on writeb. Has someone some suggestion?
Thanks in advance
Amelia
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-05-15 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 16:34 Amelia De Vivo [this message]
2001-05-15 16:58 ` Addressing PCI memory Takashi Oe
2001-05-15 17:02 ` Gabriel Paubert
2001-05-15 18:16 ` Jeff Garzik
2001-05-16 16:40 ` ashish anand
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='002f01c0dd5c$f64942e0$7a00000a@roma.quadrics.com' \
--to=amelia@roma.quadrics.com \
--cc=amelia.devivo@roma.quadrics.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).