linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Krzysztof Helt <krzysztof.h1-IjDXvh/HVVUAvxtiuMwx3w@public.gmane.org>
Cc: Linux-fbdev-devel
	<linux-fbdev-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] tdfxfb: move I2C functionality into the tdfxfb
Date: Mon, 23 Mar 2009 13:18:43 +0100	[thread overview]
Message-ID: <20090323131843.64eacafe@hyperion.delvare> (raw)
In-Reply-To: <20090323110133.7CB7186118D-UW0e3zZ4DiCOitzWlErfBcT2TbGLZofU@public.gmane.org>

On 23 Mar 2009 12:01:33 +0100, krzysztof.h1-IjDXvh/HVVUAvxtiuMwx3w@public.gmane.org wrote:
> Jean Delvare napisał(a):
> > On Sat, 21 Mar 2009 20:29:54 +0100, Krzysztof Helt wrote:
> > > +	depends on FB_3DFX >> EXPERIMENTAL
> > > +	select FB_DDC
> > > +	default y
> > > +	help
> > > +	  Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
> > 
> > It might be worth adding a note that the driver itself doesn&#039;t yet take
> > benefit of the DDC channel.
> 
> IHMO, it does not matter. A separate patch which make use of it is already
> ready to post. If this patch is accepted, the second one will be posted. It 
> is not worth to add a comment then remove it in the next patch.

Ah, very well then. I wasn't sure if you had already been working on it
or if it was just a plan for the future. If you already have a patch
implementing "full support" then I agree with you.

> > > (...)
> > > +	tdfxfb_setup_ddc_bus(>par->chan[0], "VOODOO3-DDC", info->dev);
> > > +	tdfxfb_setup_i2c_bus(>par->chan[1], "VOODOO3-I2C", info->dev);
> > 
> > Why all-caps names? What about "Voodoo3 DDC" and "Voodoo3 I2C" instead?
> > 
> 
> Just a choice. One other driver does it this way. I'll change to
> the proposed names.

The I2C bus names of framebuffer drivers have a rather bad history :(

> > Next step is to deprecate i2c-voodoo3. This requires changes to
> > drivers/i2c/busses/Kconfig and
> > Documentation/feature-removal-schedule.txt. Are you going to do it or
> > should I?
> 
> I don't care. First, this patch must be accepted.

It will be accepted, don't worry :)

I'll prepare the deprecation patch now, should be fairly trivial.

-- 
Jean Delvare

  parent reply	other threads:[~2009-03-23 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23 11:01 Re: [PATCH] tdfxfb: move I2C functionality into the tdfxfb krzysztof.h1-IjDXvh/HVVUAvxtiuMwx3w
     [not found] ` <20090323110133.7CB7186118D-UW0e3zZ4DiCOitzWlErfBcT2TbGLZofU@public.gmane.org>
2009-03-23 12:18   ` Jean Delvare [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-21 19:29 Krzysztof Helt
     [not found] ` <20090321202954.2558a62b.krzysztof.h1-IjDXvh/HVVUAvxtiuMwx3w@public.gmane.org>
2009-03-23 10:07   ` Jean Delvare

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=20090323131843.64eacafe@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=krzysztof.h1-IjDXvh/HVVUAvxtiuMwx3w@public.gmane.org \
    --cc=linux-fbdev-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).