Signed-off-by: Luke Dashjr luke-jr+...@utopios.org
---
arch/arm/mach-omap2/board-rx51-peripherals.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/board-rx51-peripherals.c
b/arch/arm/mach-omap2/board-
rx51-peripherals.c
index 9a5eb87..2c694d4
Signed-off-by: Luke Dashjr luke-jr+...@utopios.org
---
arch/arm/mach-omap2/board-rx51-peripherals.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/board-rx51-peripherals.c
b/arch/arm/mach-omap2/board-rx51-peripherals.c
index 0348392..4131cc6 100644
On Monday 07 June 2010 01:49:05 am Govindraj wrote:
Hope your are trying to use Kevins Wip-UART branch.
Since platform data support is currently available in that branch.
Nope... Google doesn't seem to know where this branch is, either. :/
ensure you have selected omap-serial driver
I'm not
On Monday 07 June 2010 08:28:51 am Govindraj wrote:
Link:
http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git;a=summa
ry
Branch:
pm-wip/uart
This branch doesn't appear to have omap-serial.c at all...
If you are trying to use with any client device connected to uart
then
On Monday 07 June 2010 02:47:34 am Tomi Valkeinen wrote:
I don't have any device that uses RFBI so I can't test it, but how about
this patch:
Unfortunately, I can't test it either since N8x0 has no mainline support for
video output, nor can until CBus is merged. :(
--
To unsubscribe from this
This doesn't even build, so I don't know how it was tested... Reverting the
offending commit (simple, but does require conflict resolution) at least lets
it compile, but I haven't tested whether it alone is enough to work in
practise yet... hoping Tomi might provide a real fix. Maybe even in
How do I actually get this to work? Built a kernel with it for my N810, but
there's no ttyO* (I'm using devtmpfs)...
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Friday 28 May 2010 02:11:29 am you wrote:
On Thu, May 27, 2010 at 9:30 PM, Luke-Jr l...@dashjr.org wrote:
On Wednesday 26 May 2010 05:48:58 pm Kevin Hilman wrote:
FYI... this also works on OMAP2.
I tested it on my n810 along with UART hwmod conversion and it works
just fine
On Wednesday 26 May 2010 05:48:58 pm Kevin Hilman wrote:
FYI... this also works on OMAP2.
I tested it on my n810 along with UART hwmod conversion and it works
just fine there.
Is it somehow different from the basic 8250 driver on OMAP2? I've been
struggling to figure out why my N810's GPS
On Friday 08 January 2010 11:03:38 pm green wrote:
Luke-Jr wrote at 2010-01-05 17:46 -0600:
* N900 is supposedly mostly mainlined already, and supposedly Nokia will
actually finish the job with unlike N8x0; it also has nicer hardware,
even if you just ignore the cellular capabilities
You
On Thursday 07 January 2010 10:55:02 am green wrote:
I would like to run Debian on my N810; have you gotten PM, gps, and
internal mmc to work while running Gentoo?
Don't expect GPS to ever work. The proprietary driver depends on a bug fixed
in 2.6.23 or so, and even ignoring that, is full of
On Thursday 07 January 2010 09:25:40 am Francisco Alecrim wrote:
Luke-Jr wrote:
On Wednesday 06 January 2010 05:59:48 pm you wrote:
Luke-Jr wrote:
Also, note my rootfs is Gentoo, not Maemo. Maemo will depend on DSME
which is not being started with my modded linuxrc.
I'm using Mamona
On Wednesday 06 January 2010 05:02:23 pm you wrote:
I'm using the flags (no-omap-wd,no-retu-wd,no-lifeguard-reset)
recommended by Kalle[1]. This's not the problem. :(
AFAIK, no-retu-wd disables *pinging* the retu WD (which itself cannot be
disabled). I'd try removing that one.
Also, note my
On Wednesday 06 January 2010 05:59:48 pm you wrote:
Luke-Jr wrote:
Also, note my rootfs is Gentoo, not Maemo. Maemo will depend on DSME
which is not being started with my modded linuxrc.
I'm using Mamona. Anyway,I did some tests before rootfs execution and I
got the same problem. My
On Tuesday 05 January 2010 05:24:56 pm Francisco Alecrim wrote:
Luke-Jr wrote:
Tested on Nokia N810 in Linux-OMAP tree. Mainline is not bootable yet.
I'm with some problems to boot-up latest l-o(commit
abb74381235a05f15a3b07e9e3831034942c67fb) with n810. The error message
can be found
On Tuesday 05 January 2010 08:46:27 pm Francisco Alecrim wrote:
Luke-Jr wrote:
On Tuesday 05 January 2010 05:24:56 pm Francisco Alecrim wrote:
Luke-Jr wrote:
Tested on Nokia N810 in Linux-OMAP tree. Mainline is not bootable yet.
I'm with some problems to boot-up latest l-o(commit
On Wednesday 30 December 2009 01:17:11 am Kalle Valo wrote:
Luke-Jr l...@dashjr.org writes:
On that topic, is there a reason the newer code is under a unified N8x0
config option instead of the split N800/N810 that was used for the old
code, or is that simply a symptom of the currently
On Tuesday 29 December 2009 02:29:22 am Kalle Valo wrote:
Luke-Jr l...@dashjr.org writes:
Tested on Nokia N810 in Linux-OMAP tree. Mainline is not bootable yet.
What's the problem in mainline? I haven't tested n8x0 for months :(
Lack of platform support, as far as I know.
Until we have cbus
On Tuesday 29 December 2009 02:55:46 am Kalle Valo wrote:
Having lots of small files is difficult IMHO.
The last-working N8x0 support (Linux-OMAP 2.6.30-rc8) required 1706 lines of
platform data and initialization, split up into 6 files:
590 N800 + i2c + FM + keyboard + light sensor
On Tuesday 29 December 2009 03:05:46 pm Luke-Jr wrote:
The last-working N8x0 support (Linux-OMAP 2.6.30-rc8) required 1706 lines
of platform data and initialization, split up into 6 files:
Upon trying to debug my non-working keyboard, I learned that the status of
mainlining is actually worse
Add platform data and initialization for USB on Nokia N800 and N810 devices
via the TUSB6010 chipset.
Tested on Nokia N810 in Linux-OMAP tree. Mainline is not bootable yet.
Signed-off-by: Luke Dashjr luke_linuxk...@dashjr.org
---
arch/arm/mach-omap2/Kconfig |5 +
How did you get this debug output? I'm hoping something other than the serial
header, since that's impractical to use at all... :/
On Thursday 17 September 2009 05:19:31 am Stefano Panella wrote:
Hi,
I have just tried to boot a kernel image using n8x0_defconfig file,
using the most
When the rx44 keymap support is added back in your quilt set, can we
discuss it. IIRC, the same kind of value (i.e. 255) is also in the
rx-51. Any specific reason?
I presume the reason is that the standard code for the Fn key is 464... so
it is only correct to map Fn to KEY_FN. ;)
There is
I noticed that the patch adding board-n8x0.c seems to be much smaller than the
older one used in Linux-OMAP. In particular, it lacks the keymaps and such.
Are those somewhere else now? Was the Linux-OMAP keyboard bug taken into
consideration for the new keyboard config struct?
Luke
--
To
Found the problem with the 2.6.29 N810 keyboard regression in this commit:
commit c83702a764c3099df50f215b8e79e07344e34a1a
Author: Felipe Balbi felipe.ba...@nokia.com
Date: Thu Feb 19 12:29:40 2009 +
input: lm8323: get rid of useless debug macro
From de992fa168685ddd608fca0f54fcfbce2afc2963 Mon Sep 17 00:00:00 2001
From: Luke Dashjr l...@dashjr.org
Date: Sat, 6 Jun 2009 16:35:03 -0500
Subject: [PATCH] arm: omap: n810: set lm8323 size_y to 12
For some reason, this is needed for the shift keys and fghjvbnm
Signed-off-by: Luke Dashjr
On Saturday 06 June 2009 05:42:04 pm Felipe Balbi wrote:
Are you sure that was the commit that changed it ?
that commit is only getting rid of the debug() macro and making use of
dev_vdbg().
Oops, looks like I put the wrong commit at fault. The correct one is:
Having trouble getting 2.6.30-rc4-omap1 to boot my US N810 (running Gentoo).
The initial problem appears to be related to /dev/mmcblk* missing, but I can't
debug it very far due to the second problem I encountered:
The keys fghjvbnm do not appear to work. I added debug info to print when
the
28 matches
Mail list logo
