All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otto Solares <solca@guug.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Carlo E. Prelz" <fluido@fluido.as>,
	James Simmons <jsimmons@infradead.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Re: FBDEV 2.6.0-test7 updates.
Date: Thu, 16 Oct 2003 15:06:43 -0600	[thread overview]
Message-ID: <20031016210643.GD19795@guug.org> (raw)
In-Reply-To: <1066298431.1407.119.camel@gaston>

On Thu, Oct 16, 2003 at 12:00:32PM +0200, Benjamin Herrenschmidt wrote:
> On Thu, 2003-10-16 at 11:19, Carlo E. Prelz wrote:
> > 	Subject: [Linux-fbdev-devel] Re: FBDEV 2.6.0-test7 updates.
> > 	Date: gio, ott 16, 2003 at 12:27:44 +0100
> > 
> > Quoting James Simmons (jsimmons@infradead.org):
> > 
> > > I applied it. I also have Ben's new driver avaiable for testing. 
> > > The diff I released uses Ben's new driver but in BK I'm stilling using teh 
> > > old driver.
> > 
> > I am the happy owner of a "Club"-branded Radeon9200 video card. Here
> > are my experiences using your diff.
> > 
> > My card has a PCI id of 5964. Here you can read the output of 'lspci
> > -vvv' for it:
> 
> My new driver (bk://ppc.bkbits.net/linuxppc-2.5-benh) now uses a copy
> of XFree PCI IDs list, making it much easier to keep in sync. It should
> also support the 9200.

I think your driver is an improvement over the old one, but:

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

- 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.

-solca



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

WARNING: multiple messages have this Message-ID (diff)
From: Otto Solares <solca@guug.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Carlo E. Prelz" <fluido@fluido.as>,
	James Simmons <jsimmons@infradead.org>,
	Linux Fbdev development list 
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Re: FBDEV 2.6.0-test7 updates.
Date: Thu, 16 Oct 2003 15:06:43 -0600	[thread overview]
Message-ID: <20031016210643.GD19795@guug.org> (raw)
In-Reply-To: <1066298431.1407.119.camel@gaston>

On Thu, Oct 16, 2003 at 12:00:32PM +0200, Benjamin Herrenschmidt wrote:
> On Thu, 2003-10-16 at 11:19, Carlo E. Prelz wrote:
> > 	Subject: [Linux-fbdev-devel] Re: FBDEV 2.6.0-test7 updates.
> > 	Date: gio, ott 16, 2003 at 12:27:44 +0100
> > 
> > Quoting James Simmons (jsimmons@infradead.org):
> > 
> > > I applied it. I also have Ben's new driver avaiable for testing. 
> > > The diff I released uses Ben's new driver but in BK I'm stilling using teh 
> > > old driver.
> > 
> > I am the happy owner of a "Club"-branded Radeon9200 video card. Here
> > are my experiences using your diff.
> > 
> > My card has a PCI id of 5964. Here you can read the output of 'lspci
> > -vvv' for it:
> 
> My new driver (bk://ppc.bkbits.net/linuxppc-2.5-benh) now uses a copy
> of XFree PCI IDs list, making it much easier to keep in sync. It should
> also support the 9200.

I think your driver is an improvement over the old one, but:

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

- 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.

-solca


  parent reply	other threads:[~2003-10-16 21:08 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 22:59 FBDEV 2.6.0-test7 updates James Simmons
2003-10-15 22:59 ` James Simmons
2003-10-15 23:17 ` Andrew Morton
2003-10-15 23:17   ` Andrew Morton
2003-10-15 23:22   ` James Simmons
2003-10-15 23:22     ` James Simmons
2003-10-15 23:20 ` Andrew Morton
2003-10-15 23:20   ` Andrew Morton
2003-10-15 23:27   ` James Simmons
2003-10-15 23:27     ` James Simmons
2003-10-16  9:19     ` Carlo E. Prelz
2003-10-16  9:19       ` [Linux-fbdev-devel] " Carlo E. Prelz
2003-10-16  9:29       ` Sven Luther
2003-10-16  9:29         ` [Linux-fbdev-devel] " Sven Luther
2003-10-17 16:48         ` James Simmons
2003-10-17 16:48           ` [Linux-fbdev-devel] " James Simmons
2003-10-16 10:00       ` Benjamin Herrenschmidt
2003-10-16 10:00         ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-10-16 10:19         ` Carlo E. Prelz
2003-10-16 10:19           ` [Linux-fbdev-devel] " Carlo E. Prelz
2003-10-16 10:41           ` Benjamin Herrenschmidt
2003-10-16 10:41             ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-10-16 10:48             ` Carlo E. Prelz
2003-10-16 10:42           ` Benjamin Herrenschmidt
2003-10-16 10:42             ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-10-17 10:04             ` Carlo E. Prelz
2003-10-17 10:49               ` Benjamin Herrenschmidt
2003-10-17 11:10                 ` Carlo E. Prelz
2003-10-17 11:10                   ` [Linux-fbdev-devel] " Carlo E. Prelz
2003-10-17 11:16                   ` Benjamin Herrenschmidt
2003-10-17 11:16                     ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-10-17 14:44                     ` Kronos
2003-10-17 17:29                       ` James Simmons
2003-10-17 17:29                         ` [Linux-fbdev-devel] " James Simmons
2003-10-18 21:28                   ` Pavel Machek
2003-10-17 17:40                 ` James Simmons
2003-10-17 17:40                   ` [Linux-fbdev-devel] " James Simmons
2003-10-17 14:26               ` Kronos
2003-10-16 21:06         ` Otto Solares [this message]
2003-10-16 21:06           ` Otto Solares
2003-10-17 10:30           ` Benjamin Herrenschmidt
2003-10-17 16:52           ` James Simmons
2003-10-17 16:52             ` [Linux-fbdev-devel] " James Simmons
2003-10-17 19:34             ` Jon Smirl
2003-10-17 19:50               ` Dave Jones
2003-10-17 19:50                 ` [Linux-fbdev-devel] " Dave Jones
2003-10-17 22:42       ` Jon Smirl
2003-10-16  0:24   ` Michel Dänzer
2003-10-16  0:24     ` [Linux-fbdev-devel] " Michel Dänzer
2003-10-16  8:19   ` Benjamin Herrenschmidt
2003-10-16  8:19     ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-10-17 16:45     ` James Simmons
2003-10-16  5:08 ` Jan De Luyck
2003-10-17 16:44   ` James Simmons
2003-10-16  5:17 ` Jan De Luyck
2003-10-16 10:44 ` Adrian Bunk
2003-10-16 10:44   ` Adrian Bunk
2003-10-16 17:48   ` James Simmons
2003-10-16 17:48     ` James Simmons
2003-10-16 19:58 ` Geert Uytterhoeven
2003-10-16 19:58   ` [Linux-fbdev-devel] " Geert Uytterhoeven
2003-10-16 20:40   ` Sam Ravnborg
2003-10-17 11:18   ` Benjamin Herrenschmidt
2003-10-17 11:18     ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-10-17 17:25     ` James Simmons
2003-10-17 17:45       ` Torrey Hoffman
2003-10-17 17:45         ` [Linux-fbdev-devel] " Torrey Hoffman
2003-10-17 17:23   ` James Simmons
2003-10-17 13:23 ` Alex Goddard

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=20031016210643.GD19795@guug.org \
    --to=solca@guug.org \
    --cc=benh@kernel.crashing.org \
    --cc=fluido@fluido.as \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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 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.