> > > > > > On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie
> > > > > > wrote:
> > > > > > > can you guys ask someone internally about it also, there is a
> > > > > > > driver somewhere in Google also for driving the LVDS->HDMI
> > > > > > > adapter but I'm not sure what i2c bus its hanging off.
> >
> > > > > > On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie
> > > > > > wrote:
> > > > > > > can you guys ask someone internally about it also, there is a
> > > > > > > driver somewhere in Google also for driving the LVDS->HDMI
> > > > > > > adapter but I'm not sure what i2c bus its hanging off.
> >
On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie wrote:
> On Tue, Mar 29, 2011 at 5:29 PM, Chris Wilson
> wrote:
>> On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury > snewbury.org.uk> wrote:
>>> Hi Chris, have you updated this patch? I have an Intel D525 (Pineview)
>>> system with HDMI port conne
On Tue, Mar 29, 2011 at 5:29 PM, Chris Wilson
wrote:
> On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury
> wrote:
>> Hi Chris, have you updated this patch? I have an Intel D525 (Pineview)
>> system with HDMI port connected through an LVDS converter. ?The "panel
>> timings" are the HDMI outpu
> > > > > On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie
> > > > > wrote:
> > > > > > can you guys ask someone internally about it also, there is a
> > > > > > driver somewhere in Google also for driving the LVDS->HDMI
> > > > > > adapter but I'm not sure what i2c bus its hanging off.
> > > > > >
>
- Original message -
>
> - Original message -
> > - Original message -
> > > - Original message -
> > > > On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie
> > > > wrote:
> > > > > can you guys ask someone internally about it also, there is a
> > > > > driver somewhere
- Original message -
> - Original message -
> > - Original message -
> > > On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie
> > > wrote:
> > > > On Tue, Mar 29, 2011 at 5:29 PM, Chris Wilson
> > > > wrote:
> > > > > On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury
> > > > >
- Original message -
> - Original message -
> > On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie wrote:
> > > On Tue, Mar 29, 2011 at 5:29 PM, Chris Wilson
> > > wrote:
> > > > On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury
> > > > wrote:
> > > > > Hi Chris, have you updated this
- Original message -
> On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie wrote:
> > On Tue, Mar 29, 2011 at 5:29 PM, Chris Wilson
> > wrote:
> > > On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury
> > > wrote:
> > > > Hi Chris, have you updated this patch? I have an Intel D525
> > > > (Pinev
- Original message -
> On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury
> wrote:
> > Hi Chris, have you updated this patch? I have an Intel D525 (Pineview)
> > system with HDMI port connected through an LVDS converter.? The "panel
> > timings" are the HDMI output mode, and it gets set t
On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury
wrote:
> Hi Chris, have you updated this patch? I have an Intel D525 (Pineview) system
> with HDMI port connected through an LVDS converter. The "panel timings" are
> the HDMI output mode, and it gets set through a BIOS option making it
> imp
> > > > > On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie
> > > > > wrote:
> > > > > > can you guys ask someone internally about it also, there is a
> > > > > > driver somewhere in Google also for driving the LVDS->HDMI
> > > > > > adapter but I'm not sure what i2c bus its hanging off.
> > > > > >
>
- Original message -
>
> - Original message -
> > - Original message -
> > > - Original message -
> > > > On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie
> > > > wrote:
> > > > > can you guys ask someone internally about it also, there is a
> > > > > driver somewhere
- Original message -
> - Original message -
> > - Original message -
> > > On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie
> > > wrote:
> > > > On Tue, Mar 29, 2011 at 5:29 PM, Chris Wilson
> > > > wrote:
> > > > > On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury
> > > > >
- Original message -
> - Original message -
> > On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie wrote:
> > > On Tue, Mar 29, 2011 at 5:29 PM, Chris Wilson
> > > wrote:
> > > > On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury
> > > > wrote:
> > > > > Hi Chris, have you updated this
- Original message -
> On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie wrote:
> > On Tue, Mar 29, 2011 at 5:29 PM, Chris Wilson
> > wrote:
> > > On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury
> > > wrote:
> > > > Hi Chris, have you updated this patch? I have an Intel D525
> > > > (Pinev
- Original message -
> On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury
> wrote:
> > Hi Chris, have you updated this patch? I have an Intel D525 (Pineview)
> > system with HDMI port connected through an LVDS converter. The "panel
> > timings" are the HDMI output mode, and it gets set t
On Tue, Mar 29, 2011 at 5:49 PM, Dave Airlie wrote:
> On Tue, Mar 29, 2011 at 5:29 PM, Chris Wilson
> wrote:
>> On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury
>> wrote:
>>> Hi Chris, have you updated this patch? I have an Intel D525 (Pineview)
>>> system with HDMI port connected through a
On Tue, Mar 29, 2011 at 5:29 PM, Chris Wilson wrote:
> On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury
> wrote:
>> Hi Chris, have you updated this patch? I have an Intel D525 (Pineview)
>> system with HDMI port connected through an LVDS converter. The "panel
>> timings" are the HDMI output
On Mon, 28 Mar 2011 22:46:55 +0100, Steven Newbury
wrote:
> Hi Chris, have you updated this patch? I have an Intel D525 (Pineview) system
> with HDMI port connected through an LVDS converter. The "panel timings" are
> the HDMI output mode, and it gets set through a BIOS option making it
> imp
Sorry, about the empty reply.
- Original message -
> On Wed, 2011-02-09 at 15:01 +, Chris Wilson wrote:
> > The LVDS code ignores any connector for which it cannot find a fixed
> > mode (through an EDID, vBIOS tables or the current active mode). Some
> > platforms may include an LVDS he
- Original message -
> On Wed, 2011-02-09 at 15:01 +, Chris Wilson wrote:
> > The LVDS code ignores any connector for which it cannot find a fixed
> > mode (through an EDID, vBIOS tables or the current active mode). Some
> > platforms may include an LVDS header on the board and this may
- Original message -
> On Wed, 2011-02-09 at 15:01 +, Chris Wilson wrote:
> > The LVDS code ignores any connector for which it cannot find a fixed
> > mode (through an EDID, vBIOS tables or the current active mode). Some
> > platforms may include an LVDS header on the board and this may
Sorry, about the empty reply.
- Original message -
> On Wed, 2011-02-09 at 15:01 +, Chris Wilson wrote:
> > The LVDS code ignores any connector for which it cannot find a fixed
> > mode (through an EDID, vBIOS tables or the current active mode). Some
> > platforms may include an LVDS he
On Wed, 2011-02-09 at 15:01 +, Chris Wilson wrote:
> The LVDS code ignores any connector for which it cannot find a fixed
> mode (through an EDID, vBIOS tables or the current active mode). Some
> platforms may include an LVDS header on the board and this may then be
> partnered with a panel wit
On Wed, 2011-02-09 at 15:01 +, Chris Wilson wrote:
> The LVDS code ignores any connector for which it cannot find a fixed
> mode (through an EDID, vBIOS tables or the current active mode). Some
> platforms may include an LVDS header on the board and this may then be
> partnered with a panel wit
The LVDS code ignores any connector for which it cannot find a fixed
mode (through an EDID, vBIOS tables or the current active mode). Some
platforms may include an LVDS header on the board and this may then be
partnered with a panel without an EDID. This results in us ignoring the
connector and not
The LVDS code ignores any connector for which it cannot find a fixed
mode (through an EDID, vBIOS tables or the current active mode). Some
platforms may include an LVDS header on the board and this may then be
partnered with a panel without an EDID. This results in us ignoring the
connector and not
28 matches
Mail list logo
