linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@softhome.net>
To: kronos@kronoz.cjb.net, adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] DDC2/I2C Support
Date: Tue, 6 Jan 2004 08:31:45 +0800	[thread overview]
Message-ID: <200401060831.46018.adaplas@softhome.net> (raw)
In-Reply-To: <20040105171639.GA7048@dreamland.darkstar.lan>

On Tuesday 06 January 2004 01:16, Kronos wrote:
> Il Mon, Jan 05, 2004 at 09:31:02AM -0500, adaplas@pol.net ha scritto:
> > 1. [fbi2c.c]:  Added preliminary generic DDC2/i2c support (derived from
> > xf86DDC.c and xf86i2.c)
> >
> > 	This is a configurable option (CONFIG_FB_I2C). 	For now, I only used
> > "default" timeout values which may not work for all devices.
> >
> > 	Most drivers need to implement only two functions --
> >
> > 		void xxxfb_i2c_getbits(struct fb_info *info, signed long *clock, signed
> > long *data)
> > 		void xxxfb_i2c_putbits(struct fb_info *info, signed long clock, signed
> > long data)
>
> In fbi2c.c you are duplicating the i2c layer that's already there in the
> kernel. Each driver should  have its set of function to  control SDA and
> SCL and then it's only a matter of calling i2c_transfer.
>
> I wrote the i2c stuff for the new radeon driver, look here:
> bk://ppc.bkbits.net/linuxppc-2.5-benh
> (drivers/video/aty/radeon_i2c.c)

Ok.  See my reply to Ben H.

>
> > 2. [fbmon.c]: Consolidated different ways of getting EDID with the
> > following function:
> >
> > 	unsigned char *fb_get_edid(struct fb_info *info, struct pci_dev *pdev,
> > int what)
> >
> > 		the parameter "what" can be:
> > 			EDID_DDC2 - get EDID via DDC2/I2C fb_get_edid_from_ddc2()
> > 			EDID_ARCH - get	EDID via BIOS or OF get_EDID_from_{OF|BIOS}()
>
> Hum, I don't like this kind of "multiplexing". I think that EDID
> reading (if possibile) should be done inside the driver which knows how
> to do it.
>
> Also, why did you remove all the printk's? Ok, show_edid is a bit too
> verbose but it's usefull for debugging.

The first time I wrote the edid parser, show_edid() was never meant to have 
all that printk's :-).  It's only preliminary code in preparation for 
extending struct fb_monspecs.  But I'll bring it back, possibly when DEBUG is 
defined.

Tony


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click

  parent reply	other threads:[~2004-01-06  0:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 14:31 [PATCH] DDC2/I2C Support adaplas
     [not found] ` <20040105171639.GA7048@dreamland.darkstar.lan>
2004-01-06  0:31   ` Antonino A. Daplas [this message]
     [not found] ` <1073339963.780.93.camel@gaston>
2004-01-06  0:31   ` Antonino A. Daplas
2004-01-06  0:42     ` Benjamin Herrenschmidt
2004-01-06  0:37 ` Benjamin Herrenschmidt

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=200401060831.46018.adaplas@softhome.net \
    --to=adaplas@softhome.net \
    --cc=adaplas@pol.net \
    --cc=kronos@kronoz.cjb.net \
    --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).