From: Jon Smirl <jonsmirl@gmail.com>
To: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: removing direct use of PCI_ROM_ADDRESS_ENABLE
Date: Thu, 17 Mar 2005 11:01:27 -0500 [thread overview]
Message-ID: <9e47339105031708016804d775@mail.gmail.com> (raw)
These drivers need to be fixed to use the new kernel ROM API.
PCI_ROM_ADDRESS_ENABLE is going to get deprecated soon. See the new
radeonfb for an example. You don't have to worry about shadow RAM
copies, the ROM code will handle it for you.
video/console/sticore.c:
pci_write_config_dword(sti->pd, PCI_ROM_ADDRESS, rom_base &
~PCI_ROM_ADDRESS_ENABLE);
video/console/sticore.c: pci_write_config_dword(pd,
PCI_ROM_ADDRESS, rom_base | PCI_ROM_ADDRESS_ENABLE);
video/matrox/matroxfb_misc.c: pci_write_config_dword(pdev,
PCI_ROM_ADDRESS, (fbbase & PCI_ROM_ADDRESS_MASK) |
PCI_ROM_ADDRESS_ENABLE);
video/sis/sis_main.c: (ivideo->video_base &
PCI_ROM_ADDRESS_MASK) | PCI_ROM_ADDRESS_ENABLE);
New routines:
/* ROM control related routines */
void __iomem *pci_map_rom(struct pci_dev *pdev, size_t *size);
void __iomem *pci_map_rom_copy(struct pci_dev *pdev, size_t *size);
void pci_unmap_rom(struct pci_dev *pdev, void __iomem *rom);
void pci_remove_rom(struct pci_dev *pdev);
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
reply other threads:[~2005-03-17 16:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9e47339105031708016804d775@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.