Re: [Linux-fbdev-devel] Re: FBDEV 2.6.0-test7 updates.

[Benjamin Herrenschmidt <benh@kernel.crashing.org>]

> - Could I2C be ported to kernel I2C api and separated?, so it use would not
> require the fbdev module loaded.

I don't plan to do that. The i2c _IS_ using the kernel i2c APIs, but
the proper DDC probing requires various other register tweaking and
I just don't want to have a separate driver tapping the radeon registers
at this point.

I'm really very much in favor of having the fbdev be the kernel API
to display devices in general, including for things like EDID retreival.

> - PCI IDs list should be in pci_ids.h as every other drivers, reality is
> that adding new IDs to pci_ids.h is not hard so your driver will not be the
> exception to the rule.

Looks like you didn't have to deal with all of the merge conflicts
that happen systematically when you have to maintain a kernel tree and 
have changes to pci_ids :)

pci_ids.h is hell to manage. Really. And it makes it a lot simpler for now,
at least until the driver is considered as final enough to be merged upstream,
to just keep a copy of the XFree IDs in there. I may do differently once the
driver is complete enough, but not at this point. And no, I'm far from beeing
the only one to decide not to use pci_ids.h :) I try to use it most of the time,
but in the case of radeonfb, it just makes things too painful for now.

Ben.