https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #245 from Kevin Brace ---
Hi Justin,
Assuming that SiI 164 is used by HP T5550 (it appears so), VT1632A is actualy a
clone of SiI 164.
Fortunately, VT1632A is mostly register compatible with SiI 164.
That being
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #21 from HuangRan ---
Hi Kevin,
>
> I saw the new bug report you filed regarding the HDMI.
> I am thinking that this bug you originally filed for (AGP related issue)
> probably existed when James wrote the
https://bugs.freedesktop.org/show_bug.cgi?id=94863
Bug ID: 94863
Summary: No signal at VGA (crt-tube) connected to DVI port of
VX900
Product: xorg
Version: unspecified
Hardware: x86 (IA32)
OS: Linux (All)
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #325 from Kevin Brace ---
(In reply to HuangRan from comment #321)
Hi Frank,
> By the way, I have verified OpenChrome UMS 0.4.0 driver on HP T510(VX900)
> platform. And on this platform, VGA from DVI-I port is
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #317 from Kevin Brace ---
(In reply to Christopher from comment #316)
Hi Christopher,
> I'm confused. There is no need for a network stack with the instructions I
> supplied, only a USB drive or two. The term
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #316 from Christopher ---
I'm confused. There is no need for a network stack with the instructions I
supplied, only a USB drive or two. The term you are looking for is "sneakernet"
;)
Puppy at the command line
https://bugs.freedesktop.org/show_bug.cgi?id=94853
--- Comment #1 from HuangRan ---
Created attachment 122783
--> https://bugs.freedesktop.org/attachment.cgi?id=122783=edit
GPG publick key
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=94853
Kevin Brace changed:
What|Removed |Added
Assignee|openchrome-de...@lists.free
https://bugs.freedesktop.org/show_bug.cgi?id=94853
Bug ID: 94853
Summary: Apply the commit privilege for OpenChrome
project(DRM/DDX/MESA)
Product: xorg
Version: unspecified
Hardware: Other
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #318 from Jeffrey Walton ---
> If compiling OpenChrome is such a problem, please ask the Puppy Linux
> developers to do it, and create a new image of with OpenChrome Version
> 0.4.0.
Often its helpful to file
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #319 from Christopher ---
@ Jeffrey -- I've been proactive. I've been sidelined --only recently-- by an
issue related tangentially to this bug (install issues), and I'm working
actively with a member of the
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #320 from HuangRan ---
Hi Christopher,
I don't know which port your issue is with. At my side, on Wyse C90LE
platform, VGA port from DVI-I is working for OpenChrome UMS 0.4.0. I have
verified it on Ubuntu 12.04
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #27 from caozong ---
Created attachment 122891
--> https://bugs.freedesktop.org/attachment.cgi?id=122891=edit
Xorg.0.log with custom debug info
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #26 from caozong ---
Created attachment 122890
--> https://bugs.freedesktop.org/attachment.cgi?id=122890=edit
add debug info in iga1_crtc_set_cursor_position
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #24 from Kevin Brace ---
(In reply to John Friend from comment #23)
Hi John,
> (In reply to HuangRan from comment #20)
>
> Hi Frank
>
> Thanks for your attention. Please take yor time and let me know when you
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #7 from John Friend ---
(In reply to Kevin Brace from comment #5)
Hi Kevin
Thanks for your comments. I totally agree with you on eliminating other
possible causes of failure. But the thing is, same T5550, DVI-VGA
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #327 from John Friend ---
(In reply to HuangRan from comment #326)
Hi Frank
What I mean was if you tested it only with LCD or did you have opportunity to
test it with crt monitor too. (I will also reply your and
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #8 from Justin Chevrier ---
(In reply to John Friend from comment #7)
> (In reply to Kevin Brace from comment #5)
>
> Hi Kevin
>
> Thanks for your comments. I totally agree with you on eliminating other
>
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #9 from Kevin Brace ---
Hi John,
I will reply to your message maybe tomorrow, but looking at the 2 logs you have
attached for VX900 chipset, I must say that there seems to be something weird
about your particular
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #11 from HuangRan ---
Hi John,
Yup, it seems T510 is relative newer than T5550 with your links. Yesterday, I
have purchased two sets of T5550 thin clients. After I receive it in next few
days, I can give a test
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #328 from HuangRan ---
(In reply to John Friend from comment #327)
> (In reply to HuangRan from comment #326)
>
> Hi Frank
> What I mean was if you tested it only with LCD or did you have opportunity
> to test it
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #12 from HuangRan ---
By the way, Friend, the "via-opensource driver" you mentioned is VIA's closed
driver(DRM code is open source) which can be downloaded from via's website? I
want to know exactly what
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #15 from John Friend ---
Created attachment 122839
--> https://bugs.freedesktop.org/attachment.cgi?id=122839=edit
xorg.log files of Openchrome 0.4.0 (VX900, VX800) and via-opensource (VX900)
tests w/ Philips 107E
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #16 from John Friend ---
Created attachment 122840
--> https://bugs.freedesktop.org/attachment.cgi?id=122840=edit
xorg.log and patch againts openchrome-0.4.0 to forcely detect VGA monitor
connected to DVI port of
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #13 from John Friend ---
(In reply to HuangRan from comment #12)
Hi Frank
via-opensource driver I used is a bit never version of semi-opensource KMS
driver available at via web site. You can check it at below
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #14 from John Friend ---
(In reply to Kevin Brace from comment #9)
Hi Kevin,
I have already tested two different crt monitors with two different DVI-VGA
adapters. Please also note that very same monitor supplies
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #18 from Kevin Brace ---
Hi John,
I will likely put default recognition of a VGA monitor feature into OpenChrome
Version 0.5.0.
That being said, I am still very much against manual settings as a general
rule, so
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #321 from HuangRan ---
By the way, I have verified OpenChrome UMS 0.4.0 driver on HP T510(VX900)
platform. And on this platform, VGA from DVI-I port is working fine.
So, to sum up, for OpenChrome UMS driver,
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #24 from Kevin Brace ---
Hi Eric,
Sorry for the bug triage to take so long.
I recently released OpenChrome Version 0.4.0, and it will be nice if you can
try the code with your thin client.
Please note that the
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #1 from HuangRan ---
Hi John,
I am wondering if HP T5550 and HP T510 is the same type of thin client or
not.
At my side, VGA from DVI-I port for my HP T510 thin client(VX900 based ASIC
too which has one DVI-D
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #2 from HuangRan ---
Created attachment 122801
--> https://bugs.freedesktop.org/attachment.cgi?id=122801=edit
HP T510 VGA from DVI-I port Xorg log
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #3 from Kevin Brace ---
I looked at the Xorg.0.log Frank has uploaded.
It appears that in his HP T510 thin client, I2C bus used to obtain EDID
(Extended Display Identification Data) is what OpenChrome calls I2C
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #4 from Kevin Brace ---
Hi John,
I think in terms of developer time attention, your problem will likely get the
most attention for a while from here on.
It took a lot of time and effort to release a new version,
https://bugs.freedesktop.org/show_bug.cgi?id=94863
--- Comment #5 from Kevin Brace ---
Hi John,
I should not throw too many things at once, but several things we will need to
consider.
- Does your DVI to VGA adapter work with other computers? (I personally have
seen a
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #24 from Kevin Brace ---
(In reply to Kevin Brace from comment #23)
>
> Hi Frank,
>
>
>
> H2 or H6 appears to be the DMA engine revision.
>
> https://www.freedesktop.org/wiki/Openchrome/DMAEngineNotes/
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #14 from HuangRan ---
Created attachment 122412
--> https://bugs.freedesktop.org/attachment.cgi?id=122412=edit
Wyse V90LE-top
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #29 from Kevin Brace ---
Hi Frank,
Assuming the IGP is Chrome 9 or is an AGP device, then a function called
via_agp_engine_init is called.
If you compare the registers being initialized here to OpenChrome DDX's
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #23 from Kevin Brace ---
(In reply to HuangRan from comment #22)
Hi Frank,
> With further kernel debugging, we found that in via_driver_load() function,
> it has the code as below:
> #if __OS_HAS_AGP
> if
https://bugs.freedesktop.org/show_bug.cgi?id=94528
--- Comment #3 from Kevin Brace ---
(In reply to HuangRan from comment #2)
Hi Frank,
> (In reply to Kevin Brace from comment #1)
> > Hi Frank,
> >
> > Interesting that the DRM or DDX is recognizing the HDMI monitor.
> >
>
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #269 from Kevin Brace ---
(In reply to HuangRan from comment #261)
Hi Frank,
> Hi Kevin/All,
>
>Yesterday, I received several thin clients which I bought two weeks ago
> as I said. That includes Wyse
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #25 from Kevin Brace ---
(In reply to HuangRan from comment #22)
Hi Frank,
> With further kernel debugging, we found that in via_driver_load() function,
> it has the code as below:
> #if __OS_HAS_AGP
> if
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #266 from Kevin Brace ---
Hi everyone,
I made several important changes to the code, so please retest the latest code
from the repository.
All the patches posted here are now obsolete.
In particular, I decided to
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #7 from HuangRan ---
(In reply to HuangRan from comment #6)
> Hi Eric,
>
> One question to ask about your Linux distribution version. Which Linux are
> you using? I see your log and found:
>
> [ 1197.389]
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #28 from Kevin Brace ---
(In reply to HuangRan from comment #21)
Hi Frank,
> Hi Kevin,
>
>
> >
> > I saw the new bug report you filed regarding the HDMI.
> > I am thinking that this bug you originally filed
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #273 from HuangRan ---
>Within my thin clients, the maximum size of the flash memory is 4GB. And
> that is why I prefer to use a ATA/SATA/CF devices instead.
>But here is a question to ask about the
https://bugs.freedesktop.org/show_bug.cgi?id=94258
--- Comment #9 from Eric ---
Created attachment 122402
--> https://bugs.freedesktop.org/attachment.cgi?id=122402=edit
Xorg.0.log.old booting Cx0
Timestamps looked odd so I'm including this too.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #9 from Eric ---
Created attachment 122398
--> https://bugs.freedesktop.org/attachment.cgi?id=122398=edit
Xorg.log after booting with only VGA connected
This is current 3/17/16 openchrome where the LVDS
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #20 from HuangRan ---
(In reply to Eric from comment #17)
> Yes, your V90LEW looks just like mine, black too. Right now, my Vx0LE (128MB
> flash, upgraded to 1GB ram) is running Lubuntu 12.04 installed onto a
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #22 from HuangRan ---
Hi Kevin,
(In reply to Kevin Brace from comment #19)
> Hi Eric,
>
> I think I have some explanations on why the cursor does not show up on your
> screen.
> The way VIA Technologies Chrome
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #45 from Benno Schulenberg ---
(In reply to HuangRan from comment #44)
> Actually I have changed my smtp setting with /~/.gitconfig file as below:
> smtpEncryption = tls
> smtpserver =
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #279 from Kevin Brace ---
(In reply to Christopher from comment #278)
Hi Christopher,
> Pardon me for not mentioning it sooner -- but rcrsn51 -- who made that HowTo
> -- has also made one for a utility of his,
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #281 from Christopher ---
Fascinating! Feel free to be technical with me -- I have The Google and Wiki
and the ability to ask questions if needed ;) Although my background is mostly
hardware at the
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #41 from HuangRan ---
Hi Kevin,
(In reply to HuangRan from comment #40)
> Hi Kevin,
>
> > Frank, do you know how to create a patch using Git?
> Do I use "git format-patch" to generate the patch?
> Or just just
https://bugs.freedesktop.org/show_bug.cgi?id=94660
Benno Schulenberg changed:
What|Removed |Added
Attachment #122480|0 |1
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #49 from Kevin Brace ---
Created attachment 122512
--> https://bugs.freedesktop.org/attachment.cgi?id=122512=edit
Fix VIA Technologies DRM AGP detection error message
Limit AGP detection to VIA Technologies
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #48 from Kevin Brace ---
(In reply to HuangRan from comment #47)
Hi Frank,
> Hi Kevin,
>
>
>Right now I have submitted my patch to dri-devel mail list for review.
> Can you see it? And what's the next
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #52 from Kevin Brace ---
Hi Frank,
I just caught a typo on your last name, so I obsoleted the previous proposed
patch I uploaded.
Sorry for that.
I have not e-mailed this patch to dri-devel or commited it to the
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #288 from HuangRan ---
Hi Kevin,
You can compare two logs(X log for latest UMS on Wyse V90LE platform DVI
port, X log for latest UMS on Wyse V90LE platform VGA port). Obviously when I
am using DVI port, the
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #287 from HuangRan ---
Created attachment 122518
--> https://bugs.freedesktop.org/attachment.cgi?id=122518=edit
X log for latest UMS on Wyse V90LE platform VGA port
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=94528
--- Comment #10 from Kevin Brace ---
(In reply to HuangRan from comment #9)
Hi Frank,
> Hi Kevin,
>
> The working one is from VIA Technologies's partial open source driver.
> James's DRM driver is not working properly
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #290 from Kevin Brace ---
(In reply to HuangRan from comment #288)
Hi Frank,
> Hi Kevin,
>
> You can compare two logs(X log for latest UMS on Wyse V90LE platform DVI
> port, X log for latest UMS on Wyse V90LE
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #59 from Kevin Brace ---
(In reply to HuangRan from comment #13)
Hi Frank,
> (In reply to Benno Schulenberg from comment #12)
> >
> > Just a note: most of the code comes originally from VIA, from their
> >
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #291 from Benno Schulenberg ---
(In reply to Kevin Brace from comment #290)
> Try that code ("git reset --hard 802544370dd827ed3488965e39804e3cb630888a"),
> and see what happens.
Again, please use 'git
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #60 from Benno Schulenberg ---
(In reply to Kevin Brace from comment #59)
> http://markmail.org/message/vutzfc65va4h554r#query:+page:1+mid:
> x4bp6vxkd7kmf3sh+state:results
>
> That thread explains the schism
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #292 from Jeffrey Walton ---
> (In reply to Kevin Brace from comment #290)
>> Try that code ("git reset --hard
>> 802544370dd827ed3488965e39804e3cb630888a"),
>> and see what happens.
>
> Again, please use 'git
https://bugs.freedesktop.org/show_bug.cgi?id=94130
--- Comment #20 from Benno Schulenberg ---
(In reply to Kevin Brace from comment #17)
> If you can do "git reset --hard (The commit ID prior to the "known device
> table" removal)," it might perform better.
There is no
https://bugs.freedesktop.org/show_bug.cgi?id=94130
--- Comment #19 from Benno Schulenberg ---
(In reply to Kevin Brace from comment #14)
> I can go with the idea of releasing OpenChrome Version 0.3.4, but I will say
> that I will need to reverse last several commits I
https://bugs.freedesktop.org/show_bug.cgi?id=94528
--- Comment #6 from HuangRan ---
(In reply to HuangRan from comment #5)
> Hi Kevin,
>
> I tried VX900 closed driver from the download link you provided and see
> HDMI port and VGA port are working fine on my platform. So
https://bugs.freedesktop.org/show_bug.cgi?id=94528
--- Comment #7 from HuangRan ---
> A correction for my comments above, I can see when VGA port is used, the
> Xserver can go into desktop and X log shows everything is working fine. For
> HDMI, it can do mode setting
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #10 from Eric ---
Created attachment 122399
--> https://bugs.freedesktop.org/attachment.cgi?id=122399=edit
Xorg.0.log file after booting with BOTH VGA and DVI
LVDS also shows up here
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=94528
--- Comment #11 from HuangRan ---
Hi Kevin,
Okay. Please feel free to let me know any issue you met when you are
compiling the kernel.
Thanks,
Frank
(In reply to Kevin Brace from comment #10)
> (In reply to HuangRan
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #61 from HuangRan ---
Hi Kevin,
I have not gotten time to go through this discussion. But in my opinion, I
fully support your point to remove legacy code(VBE, device table...) because
those modules are also
https://bugs.freedesktop.org/show_bug.cgi?id=94130
--- Comment #21 from HuangRan ---
(In reply to Benno Schulenberg from comment #19)
> (In reply to Kevin Brace from comment #14)
> > I can go with the idea of releasing OpenChrome Version 0.3.4, but I will say
> > that I
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #293 from HuangRan ---
Hi Kevin,
Okay, let me try it next week and tell the result here.
Thanks,
Frank
(In reply to Kevin Brace from comment #290)
> Sorry for not really being on top of the problem you
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #283 from HuangRan ---
Created attachment 122490
--> https://bugs.freedesktop.org/attachment.cgi?id=122490=edit
X log for latest UMS on Wyse V90LE platform
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #47 from HuangRan ---
Hi Kevin,
Right now I have submitted my patch to dri-devel mail list for review. Can
you see it? And what's the next step?
Thanks,
Frank
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=94210
--- Comment #20 from Dariusz Gadomski ---
(In reply to Kevin Brace from comment #17)
Hi Kevin
> I am a little getting lost.
> Are you saying that the current master branch OpenChrome code produces a
> blank
https://bugs.freedesktop.org/show_bug.cgi?id=94258
--- Comment #7 from Eric ---
Tested hardware: Wyse Cx0
lspci shows: 00:01.0 VGA compatible controller: VIA Technologies, Inc.
VX855/VX875 Chrome 9 HCM Integrated Graphics
Kernel: 3.2.0-23-generic-pae #36-Ubuntu
Current
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #33 from HuangRan ---
(In reply to Kevin Brace from comment #26)
> Hi Frank,
>
> I am just wondering.
> Shouldn't DRIVER_MODESET be ORed for driver_features member of drm_driver
> structure inside via_drv.c?
>
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #18 from Kevin Brace ---
(In reply to Eric from comment #8)
Hi Eric,
> Tested with current openchrome as of this date
> Current setup: Wyse Vx0LE
> lspci shows: [S3 Unichrome Pro] (rev 01),
> Dual HP LP2065
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #19 from Kevin Brace ---
Hi Eric,
I think I have some explanations on why the cursor does not show up on your
screen.
The way VIA Technologies Chrome family of IGP (Integrated Graphics Processor)
works is that it
https://bugs.freedesktop.org/show_bug.cgi?id=94130
--- Comment #13 from HuangRan ---
(In reply to Jeffrey Walton from comment #12)
> +1 here.
>
> Nearly every ISO I have tried is broken due to the Xserver crash for
> the VIA P4M900. That includes Debian, Ubuntu, Lubuntu
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #286 from HuangRan ---
Hi Kevin,
(In reply to Kevin Brace from comment #284)
> Does VGA at least work if you use a DVI to VGA adapter for Wyse V90LE?
Not working for VGA port(I use a DVI-I->VGA converter) now.
https://bugs.freedesktop.org/show_bug.cgi?id=91966
HuangRan changed:
What|Removed |Added
Attachment #122490|X log for latest UMS on |X log for latest UMS on
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #23 from HuangRan ---
Hi Eric,
(In reply to HuangRan from comment #7)
> I check my Ubuntu 12.04 installation on my VX900 platform and the default
> kernel is 3.13. And I found drm.ko and via.ko modules under
https://bugs.freedesktop.org/show_bug.cgi?id=94528
--- Comment #9 from HuangRan ---
(In reply to Kevin Brace from comment #8)
> (In reply to HuangRan from comment #7)
>
> Hi Frank,
>
> > Okay...
> > when I modify the xorg.conf file to enable HDMI, HDMI port is working
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #57 from Kevin Brace ---
Hi Frank,
I tried compiling James Simmons' developmental DRM module that supports KMS
with Linux 3.2 kernel.
It was a pretty miserable several hours I spent trying this . . .
It
https://bugs.freedesktop.org/show_bug.cgi?id=94130
--- Comment #17 from Kevin Brace ---
(In reply to HuangRan from comment #16)
Hi Frank,
> Hi Kevin,
>
>Do you mean that 0.3.4 and 0.4.0 will not support VT1632A support with
> DVI port? And as I reported in 91966 bug,
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #289 from Kevin Brace ---
(In reply to HuangRan from comment #288)
Hi Frank,
> Hi Kevin,
>
> You can compare two logs(X log for latest UMS on Wyse V90LE platform DVI
> port, X log for latest UMS on Wyse V90LE
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #54 from HuangRan ---
Hi Kevin,
(In reply to Kevin Brace from comment #48)
> Sorry for disappearing for a few days.
> I have been spending time setting up drm-openchrome repository on my local
> development
https://bugs.freedesktop.org/show_bug.cgi?id=94660
--- Comment #2 from Benno Schulenberg ---
(In reply to Kevin Brace from comment #1)
> After that one, I will commit your fix with the following section added
> after your Signed-off-by line.
>
> Acked-by: Kevin Brace
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #55 from HuangRan ---
Hi Kevin,
(In reply to Kevin Brace from comment #50)
> Hi Frank,
>
> I reviewed the patch and rewrote the patch comment section somewhat.
> I will not do this every time you create a
https://bugs.freedesktop.org/show_bug.cgi?id=94130
--- Comment #11 from Benno Schulenberg ---
(In reply to Kevin Brace from comment #10)
> I honestly did not want to delay the release of OpenChrome this long, but
> since I have already made substantial updates to the
https://bugs.freedesktop.org/show_bug.cgi?id=94130
--- Comment #15 from Kevin Brace ---
Hi everyone,
Two more things.
Based on the many commits made in the past 6 weeks or so, I know that VGA
coming out of a DVI to VGA adapter is finally working.
I verified this myself
https://bugs.freedesktop.org/show_bug.cgi?id=94528
--- Comment #8 from Kevin Brace ---
(In reply to HuangRan from comment #7)
Hi Frank,
> Okay...
> when I modify the xorg.conf file to enable HDMI, HDMI port is working too!
>
>
> Thanks,
> Frank
Is this with VIA
https://bugs.freedesktop.org/show_bug.cgi?id=94473
--- Comment #58 from HuangRan ---
Hi Kevin,
Actually I didn't recommend you do the back porting work for VIA KMS driver
because of this reason...
I remember one team is doing that when I am in AMD and this team spend
https://bugs.freedesktop.org/show_bug.cgi?id=94130
--- Comment #18 from HuangRan ---
Hi Kevin,
(In reply to Kevin Brace from comment #17)
> I will need to look into which version code works with Wyse V90LE, but it is
> possible that the version right before I removed that
https://bugs.freedesktop.org/show_bug.cgi?id=94210
--- Comment #17 from Kevin Brace ---
(In reply to Dariusz Gadomski from comment #15)
Hi Dariusz,
> Hey Kevin
>
> Ok, so if the unknown Card-id is not the problem do you see anything
> suspicious there that could be the
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #237 from Christopher ---
My test environment is X-Tahr 1b3, based on TahrPup 6.0.2 (X-Tahr is here -->
http://www.murga-linux.com/puppy/viewtopic.php?t=99849 ). You will need to boot
Puppy in another computer
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #239 from Kevin Brace ---
Hi Christopher,
I made several DVI related improvements to the code in the past 2 days.
I hate to say this, but I am skeptical that VT1632A based DVI is will work at
this point.
However,
501 - 600 of 1143 matches
Mail list logo