Hi,
Well, i also found that fbmem.c's FBIOPUT_VSCREENINFO: will always
call mxc_set_par all the time. I just put printk("Debug Number #"); in
very single function in both fbmem.c and mxcfb.c and see it seems
double function calling both in fbmem and mxcfb, with the same
function which is to write data onto framebuffer. i dunno whether this
is a big thing or what, or something board / HW specific function.
Also in fbmem.c there's module loading, mine subjected to mxcfb, as
framebuffer device.
#ifdef CONFIG_KMOD
static void try_to_load(int fb)
{
request_module("fb%d", fb);
}
#endif /* CONFIG_KMOD */
compared with vanilla kernel:
http://lxr.linux.no/linux+v2.6.22.6/drivers/video/fbmem.c#L1130
so, as i don't know what actually happen, i just let comment some
function based on vanilla. and it works. firstly, just want to know,
is there any picture in the screen ? and i get more. Advice ?
Ruckuus
On Apr 13, 7:19 pm, Akio <[EMAIL PROTECTED]> wrote:
> Dear Ruckuus：
>
> Sorry :( Right now, I don't have any real hardware to test
> my new mxc_ts.c. and also do
> some tests for rotating the LCD. But you can
> gotohttp://androidzaurus.seesaa.net to
> found out where to modify. He also provide some utility to
> do this job. I think you have
> to swap the x and y value.
>
> from
> input_set_abs_params(mxc_inputdev, ABS_X, X_AXIS_MIN,
> X_AXIS_MAX, 0, 0);
> input_set_abs_params(mxc_inputdev, ABS_Y, Y_AXIS_MIN,
> Y_AXIS_MAX, 0, 0);
>
> to
> input_set_abs_params(mxc_inputdev, ABS_X, Y_AXIS_MIN,
> Y_AXIS_MAX, 0, 0);
> input_set_abs_params(mxc_inputdev, ABS_Y, X_AXIS_MIN,
> X_AXIS_MAX, 0, 0);
>
> and
>
> from
> input_report_abs(mxc_inputdev, ABS_X, ts_sample.x_position);
> input_report_abs(mxc_inputdev, ABS_Y, ts_sample.y_position);
>
> to
> input_report_abs(mxc_inputdev, ABS_X, ts_sample.y_position);
> input_report_abs(mxc_inputdev, ABS_Y, ts_sample.x_position);
>
> BTW, would you like to share how to solve the flicking
> problem?
> I'm very wondering to know.
>
> Best Regards,
> Akio
>
> PS: I have a idea to collect all patches about i.mx31 and i.mx27.
> may be I can talk about this to Freescale, Taiwan. And hope
> the next released bsp contained those patches.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Android Internals" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-internals?hl=en
-~----------~----~----~----~------~----~------~--~---
