[Angstrom-devel] Unmutable PREFERRED_VERSION_xyz in angstrom-2007.1.conf

2007-10-21 Thread Leon Woestenberg
Hello all,

while testing newer package I noticed I could override some, and some not:

conf/distro/angstrom-2007.1.conf uses one of

PREFERRED_VERSION ?=
PREFERRED_VERSION =

for package versions.

I would like to be able to override these easily from my local.conf,
and so ?= is preferred for me.

Is it possible to change this upstream, or is there a reason to make
some package versions fully unmutable through local.conf?

Regards,
-- 
Leon

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


Re: [Angstrom-devel] Unmutable PREFERRED_VERSION_xyz in angstrom-2007.1.conf

2007-10-21 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Leon Woestenberg schreef:
 Hello all,
 
 while testing newer package I noticed I could override some, and some not:
 
 conf/distro/angstrom-2007.1.conf uses one of
 
 PREFERRED_VERSION ?=
 PREFERRED_VERSION =
 
 for package versions.
 
 I would like to be able to override these easily from my local.conf,
 and so ?= is preferred for me.
 
 Is it possible to change this upstream, or is there a reason to make
 some package versions fully unmutable through local.conf?

Some of the '=' ones were meant to make angstrom 'unbreakable', but
several developer insist on giving enough rope to hang themselves, so we
can change them to '?=' and start preparing responses like If you put
nonsense in your local.conf you void your warranty or Why are you
surprised it breaks with that local.conf?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHGwBsMkyGM64RGpERAo1XAJ9YbU2Squ7bj9zYDjUkPoOTLaDzuACffx1A
RcHl10XqZ4Up9zqG7235iBw=
=jnqF
-END PGP SIGNATURE-

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


[Angstrom-devel] Angstrom keyboard handling

2007-10-21 Thread Andrew Zabolotny
This is a second try to send this message, so I'm sorry if it's a
duplicate. Ugh, if only somebody could add application/pgp-signature
to the list of allowed MIME types for the list...

Hello!

Here is a better version of my previous keymap. I tried to squeeze
everything possible from the Zaurus keyboard.

Differences from the previous version.

1. For the '+', '-', '*' symbols (which are usually accessed via
Fn+something), if you press now it together with Shift, you'll get
keypad +, - and * respectively. Not that it matters a lot, but
sometimes this can be useful.

2. Fn+x, Fn+c, Fn+v will generate the XF86Cut, XF86Copy, XF86Paste
symbols, as designed on keyboard. Not sure what applications honor this
anyways, but now you at least have some extra keys ;)

3. The Calendar, Address, Mail, Home, Menu keys will generate
respectively XF86Calendar, XF86Phone (not the 'telephone' character
which is incorrectly generated for some other PDAs! XF86Phone is a
symbol while `telephone' is a Unicode character), XF86Mail,
XF86HomePage, Menu symbols as designed on keyboard. This change
required some modifications of the default keylaunchrc.matchbox too,
and to the config for gpe-conf keys.

4. I moved the backtick character from Fn+Q to Shift+'-' where it seems
more appropiate.

5. Reverted console scrolling to Fn+Shift+Up/Down (e.g.
Shift+PgUp/PgDn). Fn+Ctrl+Up/Down was pretty non-obvious to me,
couldn't get used to it.

Unfortunately, Caps Lock doesn't work. This seems a limitation of the X
server itself, which always expects the CapsLock symbol to be in column
1 to work (e.g. CapsLock must be the primary key meaning), while on
Zaurus CapsLock stays on the Tab key.

Since the list does not allow attaches with funny extensions, and I
have to attach many files, and many wouldn't like the extra load on the
mailing list I have packed everything into a single zip file here:
http://cs.ozerki.net/zap/zaurus-c3xxx-keyboard.zip

Does it make sense to try push these changes into OE?

-- 
Andrew

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


Re: [Angstrom-devel] Angstrom keyboard handling

2007-10-21 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Andrew Zabolotny schreef:

 Since the list does not allow attaches with funny extensions, and I
 have to attach many files, and many wouldn't like the extra load on the
 mailing list I have packed everything into a single zip file here:
 http://cs.ozerki.net/zap/zaurus-c3xxx-keyboard.zip
 
 Does it make sense to try push these changes into OE?


Please attach an mtn diff to the OE bugtracker.

regards,

Koen

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHG7HlMkyGM64RGpERAiwbAJ9e5jsfdGyr7iXjlKUNownJsw34cgCgkSGo
HCEeTJXoMfUY3BZd1sOHXBc=
=S970
-END PGP SIGNATURE-

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


[Angstrom-devel] Problems with screen blanking on h2200

2007-10-21 Thread Dmitry Artamonow
Sorry for probably off-topic, but [EMAIL PROTECTED] seems to be long
time dead, and I don't know where else I can post kernel-related 
problems. I would be glad if someone can clarify current situation 
with handhelds kernel developement. 

Anyway, here's my story. Recently I've been playing with Gentoo on my
h2200. After compiling xorg-server-1.4 (full-blown, not the kdrive version),
I tried to start it - but without success. Screen flickered, turned
black, then flickered again and slowly turned white instead of showing X
cursor. X server itself didn't show any error in console or logs and worked
until ^C was pressed. But even after ^C screen never returned to normal 
state until reset.

I tried to run X under strace and noticed this calls:
ioctl(6, FBIOBLANK, 0x1)= 0
and then near the end of strace log:
ioctl(6, FBIOBLANK, 0)  = 0

This seemed to be the cause, because I already experienced similar
problems with blanking in plain console and was pressed to workaround it 
with setterm -blank 0. Simple testcase program in C proved it, and 
also I found that bug can be triggered from command line by following
statements:
echo 1  /sys/class/graphics/fb0/blank 
echo 0  /sys/class/graphics/fb0/blank 

For assuring myself what it's not the fault of my custom kernel config,
I checked also with LiveRam Angstrom image (20070922) and successfully
triggered this bug from command line. 

Then I dug into kernel code, but since I'm not a kernel hacker at all, 
the only thing I tried was commenting out mq1100fb_power call from 
mq1100fb_blank function in drivers/video/mq1100fb.c :
--
diff -u -r1.45 mq1100fb.c
--- drivers/video/mq1100fb.c18 Jul 2007 19:21:42 -  1.45
+++ drivers/video/mq1100fb.c21 Oct 2007 08:25:30 -
@@ -318,7 +318,7 @@
 *blank_mode == 4: powerdown
 */
 
-   mq1100fb_power (info, blank_mode);
+/* mq1100fb_power (info, blank_mode); */
 
return 0;
 }
 

--
Suddenly it turned out to be a solution - screen was blanking anyway 
(seemed that it's somehow handled by drivers/video/backlight/h2200_lcd.c 
driver (and maybe backlight driver too)), but on unblanking it has all of 
its contents intact and X finally worked. Still I can't understand how it 
works and how screen blanking differs from device suspending which seemed 
to call the same mq1100fb_power without any problems.

--
Best regards,
Dmitry MAD Artamonow



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel