Active Topics
-
Phone Camera Competition April 2021: "Funny & Foolish" (33)
to General by Fellfrosch - 5 hrs, 42 mins ago -
What's the best Handheld gnu/linux machine for 20XX? (78)
to Competitors by clort - 10 hrs, 28 mins ago -
Unofficial Storage for camera phone competition... (62)
to General by catbus - 18 hrs, 48 mins ago -
Maemo-Leste pre-alpha announcement (512)
to Maemo 7 / Leste by nonsuch - 1 day, 19 hrs ago -
The Intel RealSense Smartphone prototype (0)
to Competitors by n950 - 1 day, 22 hrs ago -
Maemo Leste Playground (57)
to Maemo 7 / Leste by clort - 2 days, 19 hrs ago -
A Palm OS thread ... and a thank you to the community (23)
to Alternatives by bradvesp - 3 days, 19 hrs ago -
SailfishOS on Sony Z3 Compact Tablet (180)
to SailfishOS by ogustbiller - 6 days, 22 hrs ago - more...
 |
|
2009-01-25
, 23:08
|
|
Posts: 4,707 |
Thanked: 4,643 times |
Joined on Oct 2007
@ Bulgaria
|
#52
|
And has SSL? 
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
|
|
2009-01-26
, 06:36
|
|
Posts: 607 |
Thanked: 296 times |
Joined on Jun 2008
@ Finland
|
#54
|
Originally Posted by Bundyo
It's FF 3.1 beta 2, i don't know if it shoud have..
And has SSL?
__________________
Touch Book .. do not waste you money on it.
Touch Book .. do not waste you money on it.
|
|
2009-01-26
, 06:56
|
|
Posts: 4,707 |
Thanked: 4,643 times |
Joined on Oct 2007
@ Bulgaria
|
#55
|
I meant that Midori/WebKit Gtk doesn't support self-signed certificates
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
|
|
2009-01-26
, 07:55
|
|
Posts: 2 |
Thanked: 0 times |
Joined on Jan 2009
|
#56
|
Hi, can someone post step-by-step instruction? I install both files from Mer page on wiki.maemo.org, but I can`t mount my Mer partition. 
I`m try to install Mer on N800.
I`m try to install Mer on N800.
 |
|
2009-01-26
, 13:36
|
|
Posts: 17 |
Thanked: 5 times |
Joined on Jul 2008
@ Brno
|
#57
|
I spent this weekend playing with N810 external keyboard and looking why doesn't work as in Maemo. I have no solution yet, but I can name the problem. Xorg and HAL. Xorg depend on HAL, which should provide keyboard info. HAL will recognize hardware keyboard as "Internal keyboard", working with evdev driver.
Problem is, that Fn key is sending keycode 464 (according to /usr/include/linux/input.h it's really right keycode for FN key), but X server can't handle keycode > 255.
It seems, that Xomap use some ugly hack for this key (see this: https://bugs.maemo.org/show_bug.cgi?id=3021) and remap keycode 464 to 216.
I tried to use HAL to remap keyboard and I created following fdi:
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<!-- These are raw scancodes produced by the atkbd driver -->
<match key="info.product" string="Internal keyboard">
<append key="input.keymap.data" type="strlist">0x1d0:chat</append>
<append key="info.capabilities" type="strlist">input.keymap</append>
</match>
</device>
</deviceinfo>
This should remap key 464 to 216(chat). In lshal, I can see my new rule
root@michal-tablet:~# lshal | grep keymap
info.capabilities = {'input', 'input.keyboard', 'input.keys', 'button', 'input.keymap'} (string list)
input.keymap.data = {'0x1d0:chat'} (string list)
But Xorg still don't catch any keycode for Fn key. Any suggestion how to continue? I would like to find clear solution using HAL, instead of dirty hacking evdev driver
Problem is, that Fn key is sending keycode 464 (according to /usr/include/linux/input.h it's really right keycode for FN key), but X server can't handle keycode > 255.
It seems, that Xomap use some ugly hack for this key (see this: https://bugs.maemo.org/show_bug.cgi?id=3021) and remap keycode 464 to 216.
I tried to use HAL to remap keyboard and I created following fdi:
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<!-- These are raw scancodes produced by the atkbd driver -->
<match key="info.product" string="Internal keyboard">
<append key="input.keymap.data" type="strlist">0x1d0:chat</append>
<append key="info.capabilities" type="strlist">input.keymap</append>
</match>
</device>
</deviceinfo>
This should remap key 464 to 216(chat). In lshal, I can see my new rule
root@michal-tablet:~# lshal | grep keymap
info.capabilities = {'input', 'input.keyboard', 'input.keys', 'button', 'input.keymap'} (string list)
input.keymap.data = {'0x1d0:chat'} (string list)
But Xorg still don't catch any keycode for Fn key. Any suggestion how to continue? I would like to find clear solution using HAL, instead of dirty hacking evdev driver
|
|
2009-01-26
, 14:50
|
|
Posts: 607 |
Thanked: 296 times |
Joined on Jun 2008
@ Finland
|
#58
|
Any key of my n810:s hw-keyboard isn't working in Mer atm.
__________________
Touch Book .. do not waste you money on it.
Touch Book .. do not waste you money on it.
|
|
2009-01-26
, 14:56
|
|
Posts: 17 |
Thanked: 5 times |
Joined on Jul 2008
@ Brno
|
#59
|
They works for me, just without fn button... try to:
1. Delete InputDevice for keyboard from xorg.conf. All informations will come from HAL.
2. Install xserver-xorg-input-evdev
3. Restart HAL
4. Restart xorg
1. Delete InputDevice for keyboard from xorg.conf. All informations will come from HAL.
2. Install xserver-xorg-input-evdev
3. Restart HAL
4. Restart xorg
|
|
2009-01-26
, 15:07
|
|
Posts: 607 |
Thanked: 296 times |
Joined on Jun 2008
@ Finland
|
#60
|
yeah i know, keyboard was working in 0.6 release. But all keys of n8x0 hw-keyboard are dead in later versions made with imager
__________________
Touch Book .. do not waste you money on it.
Touch Book .. do not waste you money on it.
 |
| Tags |
| mer, mer release |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
All times are GMT. The time now is 15:40.
Touch Book .. do not waste you money on it.