[linux-cirrus] Re: Testing 2.6.13 git tree
- From: Michael Burian <dynmail1@xxxxxxxxxxxxxxxxx>
- To: linux-cirrus@xxxxxxxxxxxxx
- Date: Mon, 03 Oct 2005 08:02:50 +0200
llandre wrote:
> Hi Michael,
>
> today I tried to clone the repository with git 0.9.6 and it failed (it
> is strange because 10 days ago I was able to do that with the same
> version of git ...). So I switched to latest git version (0.99.7.GIT)
> and it worked fine.
> Secondly I'm testing this kernel on my board but I can't make the
> framebuffer to work :(
> I use the same settings that worked fine with 2.6.9-ep93xx-rc2:
>
That's rather old :(
> /*
> 240x320 Hitachi
>
> Max pixel clock freq = 1/83ns ~= 12.048 MHz (VDiv = 0x0000c10a)
> Typ pixel clock freq = 5.33 MHz (VDiv = 0x0000c125)
> */
> TIMING_VALUES("Hitachi TX09D50VM1CCA", CRT_GENERIC,
> (fRasterConfigure)NULL,
> 0, 0x0000c125, 240, 16/*HFP*/, 12/*HBP*/, 5/*HSYNC*/, 320,
> 3/*VFP*/, 3/*VBP*/, 1/*VSYNC*/),
>
>
> I think the fb driver changed and so I have to tune these settings
> accordingly. Any hints?
>
Let's hope it works with linux-2.6.11.7-ep93xx, otherwise we'll have
to look for backups from the bitkeeper era. I really hope that won't
be neccessary.
In case it does work, try to isolate the problem,
hints for tracking it down:
I usually create a seperate directory and fill it with all the
kernel versions in question. Then find a version that works, and
one that does not. Try to see if the version between still does work.
Once you've found the point where it stops working, you can go down to
file level and use side-by-side comparison tools like xxdiff, meld,
kompare, ... to see what change might have introduced the bug.
Unfortunately we can't use git bisect for stuff that happend before
the git transistion. :(
ps.
OK - I know this won't help you much now, but I'd recommend to test
every single version of my patches (there aren't that many, usually 1-2
per mainline patchlevel) and send me feedback (works / does not work)
immediately.
Thanks for testing!
Other related posts:
