linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@yahoo.com>
To: Ian Romanick <idr@us.ibm.com>
Cc: fb-devel <linux-fbdev-devel@lists.sourceforge.net>,
	dri-devel <dri-devel@lists.sourceforge.net>
Subject: Re: [Dri-devel] Two Linux framebuffer patches, Radeon and Rage128
Date: Sun, 10 Aug 2003 20:57:43 -0700 (PDT)	[thread overview]
Message-ID: <20030811035743.49382.qmail@web14903.mail.yahoo.com> (raw)
In-Reply-To: <3F36CAC5.7060504@us.ibm.com>

As far as I know linux/pci_ids.h is not being
generated, it is hand built. That probably explains
why it had about 15 entries in it that were wrong for
the Radeon/Rage128.

My understanding is that drivers/pci/pci.ids is
semi-hand built. It is partially generated from
http://pciids.sf.net/ and then hand diffed. It can be
config'ed out of the kernel by unchecking PCI
Names/PCI_CONFIG_NAMES. When there are no pretty name
available from PCI names then I generate one from chip
ID and PCI ID. This name is only used to log the
sign-on message so that you know the driver loaded and
found your card.

I would like to find a more authoritative database of
which chip family the various chip IDs belong to. I
would also like to know for sure whether each is PCI,
AGP, or secondary. Is there a way to get this info
from the cards themselves and not hardcode it? It also
would be nice to have a scipt to generate the code for
the drivers, but we need a good database to run it
against.

I'm working on the embedded Mesa code. Embedded Mesa
does not use XFree xf86PciInfo.h, instead it relies on
the Linux framebuffer drivers to identify the cards
via the modules/PCI hotplug system. The Rage128/Radeon
framebuffer drivers are not heavily used so I'm being
forced to update them. 

Embedded Mesa does need chip family info and PCI/AGP
status. I should probably modifiy the framebuffer
drivers to make this info accessible. Right now the
embedded Mesa drivers regenerate it based on chip ID
thus duplicating the chip ID/family data. 

For Linux the best solution would be to simply merge
the framebuffer and 3D drivers into a single driver. A
lot of duplicated code would be eliminated. That would
solve other problems too like locking and register
stomping.


=====
Jon Smirl
jonsmirl@yahoo.com

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

  reply	other threads:[~2003-08-11  3:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-09 20:41 [Dri-devel] Linux kernel PCI IDs vs Xfree Alexander Stohr
2003-08-10  4:20 ` Jon Smirl
2003-08-10  6:00 ` More Linux kernel PCI IDs vs Xfree - Radeon Jon Smirl
2003-08-10 21:32   ` Two Linux framebuffer patches, Radeon and Rage128 Jon Smirl
2003-08-10 22:44     ` [Dri-devel] " Ian Romanick
2003-08-11  3:57       ` Jon Smirl [this message]
2003-08-12  7:08         ` Jon Smirl
2003-08-10 14:07 ` [Dri-devel] Linux kernel PCI IDs vs Xfree Dave Jones
2003-08-10 15:07   ` Jon Smirl

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=20030811035743.49382.qmail@web14903.mail.yahoo.com \
    --to=jonsmirl@yahoo.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=idr@us.ibm.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 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).