mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sylvain Meyer <sylvain.meyer@worldonline.fr>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, akpm@osdl.org
Subject: Re: [Linux-fbdev-devel] [PATCH] [git tree] Intel i9xx support for intelfb
Date: Thu, 23 Mar 2006 18:57:05 +0100	[thread overview]
Message-ID: <4422E171.1040909@worldonline.fr> (raw)
In-Reply-To: <21d7e9970603222209r45beeb99nccc6435b99b79154@mail.gmail.com>

        Sorry for my very long silence.

For i2c support. I've done it to have a workable tv-out on my hardware. 
It was the main reason  why i ported the driver to kernels 2.6 as i use 
my computer as a set-top-box only connected to a tv. I've it on my own 
tree (very old).
I can send you the code. I did it in a way not accepted by kernel 
reviewers as my tv driver (for chrontel ch7011 chipset) is all in kernel 
space. But it can be a base for a better scheme.

Regards
Sylvain

Dave Airlie a écrit:

>>>This code isn't perfect but I've got no documentation so I cannot
>>>answer some questions on what exactly is going on just yet...
>>>      
>>>
>>Better than nothing, and if it works for digital displays, then that
>>would be great.
>>    
>>
>
>It doesn't support LVDS or DVI yet but I'm hoping to make it go in
>that direction, I've no LVDS h/w, and some chipsets have it integrated
>and some don't, but this is a better basis for future work, and I'll
>have no problems keeping it updated with fixes as they come from the
>X.org driver... I'd like to get at least LVDS support working for
>laptop users with these chipsets, getting DVI working is a bit more
>work as there are external chips that need to be driven over i2c, so
>I'll need to at least add i2c support to the i8xx driver. (I noticed
>Sylvain has done some of this work before)..... I'd like to expose i2c
>buses to userspace anyways....
>
>  
>
>>There's no git tree for the framebuffer layer, I just send updates
>>directly to akpm. Andrew?
>>
>>    
>>
>
>I'd like to keep the git history if possible, so maybe we can pull
>this tree into -mm and I can get it pulled by Linus later.
>
>Regards,
>Dave
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by xPML, a groundbreaking scripting language
>that extends applications into web and mobile media. Attend the live webcast
>and join the prime developer group breaking into this new coding territory!
>http://sel.as-us.falkag.net/sel?cmd=k&kid\x110944&bid$1720&dat\x121642
>_______________________________________________
>Linux-fbdev-devel mailing list
>Linux-fbdev-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
>
>  
>




  parent reply	other threads:[~2006-03-23 17:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23  2:20 Dave Airlie
2006-03-23  5:59 ` [Linux-fbdev-devel] " Antonino Daplas
2006-03-23  6:01   ` Andrew Morton
2006-03-23  6:09   ` Dave Airlie
2006-03-23 13:06     ` Antonino A. Daplas
2006-03-23 22:29       ` Sylvain Meyer
2006-03-23 17:57     ` Sylvain Meyer [this message]
2006-03-23 22:28       ` Dave Airlie
2006-03-23 22:40         ` Sylvain Meyer

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=4422E171.1040909@worldonline.fr \
    --to=sylvain.meyer@worldonline.fr \
    --cc=akpm@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome