ne, it
can't as the earlier fb has a lock on. I've tried to unregister it, but
without success. And when I do a query on what framebuffers are registered,
it shows 0 (registered_fb).
kolmapäev, 14. märts 2012 15:30.20 UTC+2 kirjutas Rudolf Tammekivi:
>
> After closer inspection,
After closer inspection, the fbcon seems to have some kind of "lock" that
doesn't allow other frame buffer to take over.
It gives a "BUG: Scheduling while atomic" on the screen, after that there
are many stack trace and then it crashes.
I've tracked the position aswell, drivers/video/fbmem.c,
Apparently, it's not entirely solved. When I have enabled framebuffer
console, msm_fb fails to load - gets stuck at register_framebuffer, any
ideas on that?
esmaspäev, 12. märts 2012 9:52.16 UTC+2 kirjutas Rudolf Tammekivi:
>
> Another thing solved. The problem was with the dis
Another thing solved. The problem was with the display driver, which had
some bugs. It's working now :)
pühapäev, 11. märts 2012 10:38.21 UTC+2 kirjutas Rudolf Tammekivi:
>
> Hello,
>
> I am porting a 3.0.8 kernel for my MSM7X30 device, but it seems to crash
> some
Hello,
I am porting a 3.0.8 kernel for my MSM7X30 device, but it seems to crash
somewhere after the main init_machine call. Can I enable frambuffer console
to start earlier or can I use some other ways to get the logs? I don't have
a serial cable, neither does the phone.
Regards,
Rudolf.
--
Every time I post here, I will find an answer myself, just like this time.
The problem was in the MDDI_BASE_ADDR, which got wrong due to a stupid
mistake.
Rudolf.
esmaspäev, 5. märts 2012 17:21.19 UTC+2 kirjutas Rudolf Tammekivi:
>
> Hello,
>
> I am currently trying to make my
Hello,
I am currently trying to make my MDDI display work on MSM7230, for fbcon on
little kernel. The display is started on the early boot, so I can leave out
the display power on commands, right? It fails at the part where it does
CMD_RESET. It gives the writel command, but it doesn't get any
in it, one of them would be boot.img.
Regards,
Rudolf.
teisipäev, 28. veebruar 2012 19:19.19 UTC+2 kirjutas Rudolf Tammekivi:
>
> Hello again,
>
> This time I need a little help on how to execute boot.img from the fat
> partition I made. Can I create a partition table, where
Hello again,
This time I need a little help on how to execute boot.img from the fat
partition I made. Can I create a partition table, where it should load
the partition and then search for boot image inside or how does it
work?
Platform is MSM7230 and the card is EMMC.
Regards,
Rudolf.
--
unsu
am content is cleared. Ram data is cleared only when battery is
> removed.
>
> On Wed, Feb 8, 2012 at 9:04 PM, Rudolf Tammekivi wrote:
>
>
>
>
>
>
>
>
>
> > Hello,
>
> > I have a device that has MMC card inside, with the partition table. My
> >
Hello,
I have a device that has MMC card inside, with the partition table. My
question is, if "panic" happens, can I use apanic module to save the log to
MMC not to the MTD partition? I did try ram_console, but the problem with
that is, my device's RAM is cleared out after restart, so I can't g
As I understand, when panic happens, RAM stays full of memory. Then,
when reboot, ram_console checks if there is a sig with the data, and
then writes it to last_kmsg, right?
On Feb 3, 1:33 pm, Rudolf Tammekivi wrote:
> I think I managed to get ram_console working on the working kernel, it
&g
I think I managed to get ram_console working on the working kernel, it
gives this in kmsg:
<6>[1, swapper] [0.256378] ram_console: got buffer at 3a0,
size 4
<6>[1, swapper] [0.256408] ram_console: no valid data in buffer
(sig = 0x20008808)
<6>[1, swapper] [0.256561] console [ra
& as well
> as non-working kernel [your case].
> Boot the non-working kernel first & try to boot the working kernel & get
> the crash log.
>
> BR, Jagan.
>
> On Mon, Jan 30, 2012 at 6:44 PM, Rudolf Tammekivi wrote:
>
>
>
>
>
>
>
> > I said i
P code.
>
> Once you have any crash/hang happening on your device, for next the reboot
> try to dump the log from
> /proc/last_kmsg [where you can get the previous crash log]...debug it
>
> Regards,
> Jagan.
>
> On Wed, Jan 25, 2012 at 7:26 PM, Rudolf Tammekivi wrote:
>
&g
rk and get a start somewhere.> there is a debug
> procedure called, RAM_CONSOLE, find it on google[enough
>
> info]
>
> Regards,
> Jagan.
>
> On Tue, Jan 24, 2012 at 9:29 PM, Rudolf Tammekivi wrote:
>
>
>
>
>
>
>
> > It's MSM7x30, and
hem on msm-3.0.
>
> Be-careful you need to do it in a procedural way.
>
> Regards,
> Jagan.
>
> On Sat, Jan 21, 2012 at 11:46 PM, Rudolf Tammekivi
> wrote:
>
>
>
>
>
>
>
> > My device has 2.6.35.7 source code provided, but I want to upgrade it to
My device has 2.6.35.7 source code provided, but I want to upgrade it to
3.0. Most of the 2.6.35.7 sources are from CodeAurora, which are modifed by
manufacturer, and I have already downloaded the 3.0 base for msm. What are
the mandatory things I need to modify in order to make it boot? Like CPU
18 matches
Mail list logo
