Hi Werner,
Thank you for the reply.
>You mean you want to have a boot menu (instead of the current u-boot
>menu) that uses the touch screen ?
Yes. I want a Graphical UI instead of the character based uboot menu ui.
Which will have 2 big icons showing Qtopia & Android. When user selects
that par
ramsarvan wrote:
> I want to have a boot menu which shows the touch based
> platform selection options.
You mean you want to have a boot menu (instead of the current u-boot
menu) that uses the touch screen ?
> Is that possible to do?
That would certainly be possible to do, but ... may I suggest
ramsarvan wrote:
> It works :)
Congratulations ! :-)
- Werner
___
devel mailing list
devel@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/devel
Hi All,
I want to have a boot menu which shows the touch based
platform selection options.
Means that I have a Android kernel that works
for both Android & Qtopia.
Is that possible to do? Since I googled a lot for
this but could not get a related link. Previously,
I remember I saw a video show
Thank you much Werner.
It works :)
Sorry for not mentioning properly. I have GTA02.
I was trying out the command in NOR Boot mode & didn't work.
Then I tried the command in NAND Boot mode and it worked.
Ram.
Werner Almesberger wrote:
>
> ramsarvan wrote:
>> Used the perl script you mentioned
On Fri, Dec 26, 2008 at 9:05 PM, Werner Almesberger wrote:
> Nelson Castillo wrote:
>> A feature I would say :-) This is even better than what we have in the
>> stable kernel because we discard noise. Sometimes the last few events
>> get discarded because they do not provide reliable data, for in
ramsarvan wrote:
> Used the perl script you mentioned and I am now getting the same 17216
> bytes after compression.
Much better ! ;-)
> But still I am not getting the splash image and I m seeing the words
> poweroff at the top left corner.
Seems that you're still using the GTA01 framebuffer ad
Hi Werner,
Thanks for the reply.
>This is strange. When I try this image (*), I get an output of
>17216 bytes after compression.
Used the perl script you mentioned and I am now getting the same 17216
bytes after compression.
So, I have given the following command in the U-Boot NOR Flash mode,
Nelson Castillo wrote:
> A feature I would say :-) This is even better than what we have in the
> stable kernel because we discard noise. Sometimes the last few events
> get discarded because they do not provide reliable data, for instance
> because not much pressure is applied.
Discarding bogus
On Fri, Dec 26, 2008 at 8:08 PM, Werner Almesberger wrote:
> Nelson Castillo wrote:
>> That is because when we get an IRQ we gather as many samples
>> as the filters need in order to produce a point, and only then we check
>> if the touchscreen is still pressed.
>
> Hmm, but is this a bug or a fea
Nelson Castillo wrote:
> That is because when we get an IRQ we gather as many samples
> as the filters need in order to produce a point, and only then we check
> if the touchscreen is still pressed.
Hmm, but is this a bug or a feature ? :-) Samples you get when the
touch screen is no longer presse
> | couldn't get. I recognize that it is more easy for some people to work
> on the
> | kernel but it is also true that writing a filter for ts_lib is very very
> | simple. I'm confident that I could move the code of your filters into
> userspace
> | and write it as module for tslib.
>
> Of course
2008/12/26 Nelson Castillo :
> Hello.
>
> With the latest kernel we can use the Touchscreen with no further
> user-space filtering. I'd like to test this.
>
> How can I make Xglamo read the TS information from /dev/input/eventX?
I agree with Holger on most points, but to answer the question other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Friday 26 December 2008 22:36:42 Andy Green wrote:
|
|> No the kernel touchscreen filter stuff is independent of the driver, it
|> is implemented separately and resuably.
|
| Ah okay. From my non existing
On Friday 26 December 2008 22:36:42 Andy Green wrote:
> No the kernel touchscreen filter stuff is independent of the driver, it
> is implemented separately and resuably.
Ah okay. From my non existing knowledge of the code I think using a
input_handler to export a "calibrated, normalized..." touc
On Fri, Dec 26, 2008 at 4:08 PM, Holger Freyther wrote:
> On Friday 26 December 2008 21:38:14 Andy Green wrote:
>
>> | for evdev and the calibration data?
>>
>> It's a good point, is there a way to associate the input event devicets_raw
>> ande s
>> that sends coordinates with the way that you se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Friday 26 December 2008 21:38:14 Andy Green wrote:
|
|> | for evdev and the calibration data?
|>
|> It's a good point, is there a way to associate the input event device
|> that sends coordinates with the
On Friday 26 December 2008 21:38:14 Andy Green wrote:
> | for evdev and the calibration data?
>
> It's a good point, is there a way to associate the input event device
> that sends coordinates with the way that you set its calibration?
With tslib? Yes. in the ts.conf you define which input_raw wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|>>> With the latest kernel we can use the Touchscreen with no further
|>>> user-space filtering. I'd like to test this.
|>> What is the benefit?
|> Briefly stated: We think it's better if the driver sends on
ramsarvan wrote:
> 1) Downloaded the perl script from
> http://svn.openmoko.org/developers/werner/splash/imghs.pl
Oh dear, there you found something really ancient. It still works,
but the current version is here:
http://svn.openmoko.org/trunk/src/host/splash/
> 7) ls -l gives the filesize as 245
#1933: usb network connection flaky
--+-
Reporter: olberger | Owner: openmoko-devel
Type: defect| Status: new
Priority: normal| Milestone:
Component: unknow
On Friday 26 December 2008 17:31:31 you wrote:
> On Fri, Dec 26, 2008 at 4:48 AM, Holger Freyther wrote:
> > On Friday 26 December 2008 06:24:21 Nelson Castillo wrote:
> >> Hello.
> >>
> >> With the latest kernel we can use the Touchscreen with no further
> >> user-space filtering. I'd like to tes
Hi All,
I tried modifying the uboot splash and did the following steps:
1) Downloaded the perl script from
http://svn.openmoko.org/developers/werner/splash/imghs.pl
2) chmod a+rx *.pl
3) Installed the netpbm
4) Taken the image file (older splash screen) from
http://wiki.openmoko.org/images/c/c2/
On Fri, Dec 26, 2008 at 4:48 AM, Holger Freyther wrote:
> On Friday 26 December 2008 06:24:21 Nelson Castillo wrote:
>> Hello.
>>
>> With the latest kernel we can use the Touchscreen with no further
>> user-space filtering. I'd like to test this.
>What is the benefit?
Briefly stated: We think it'
On Friday 26 December 2008 06:24:21 Nelson Castillo wrote:
> Hello.
>
> With the latest kernel we can use the Touchscreen with no further
> user-space filtering. I'd like to test this.
What is the benefit? How is the /etc/pointercal loaded?
z.
___
deve
25 matches
Mail list logo
