On Fri, 02 Dec 2011 19:19:49 -0500
Paul Fox p...@laptop.org wrote:
http://wiki.laptop.org/go/OLPC_Firmware_q4c07
this is primarily an EC release. it has numerous battery system
changes, and it introduces support for preserving the keystroke which
causes a system resume,
FWIW, my C1 will
On Sat, 03 Dec 2011 14:21:23 -0500
Paul Fox p...@laptop.org wrote:
FWIW, my C1 will not boot with this version. Silly me, I didn't note what
release it had initially...q4c06 also fails (everything just stops after
it tries to jump to the kernel), but q4c01 works. I can bisect it to the
On Wed, 27 Jul 2011 18:07:13 +0100
Peter Robinson pbrobin...@gmail.com wrote:
I know in Fedora 16 there were a number of tools that didn't play well with
the 3.0 (likely not a complete problem as I think the final release was in
fact 3.0.0) and the 2.6 numbering schemes.
Seemingly there
On Wed, 27 Oct 2010 16:23:10 +0100
Daniel Drake d...@laptop.org wrote:
Testing with clean linux-next as of today. 2 via-camera issues:
If that's all that goes wrong we've come a fair ways...:)
1. Approx 13 VIA DMA timeout! messages are printed every second
That seems undesirable. In the
[Sorry for the slow response...naturally enough I'm in Europe and
falling behind on things.
On Thu, 10 Jun 2010 18:01:34 -0400
Paul Fox p...@laptop.org wrote:
I doubt it is directly related to locking.
If (as you say) there is no crash in the logs then I suspect it is
related to an
On Sun, 14 Mar 2010 00:00:04 +0100
Sascha Silbe sascha-ml-ui-sugar-olpc-de...@silbe.org wrote:
One of your somewhat recent commits, 2671e48d [1], broke the camera on
XO-1.
I saw the bug entry, yes.
The TWSI port is Vdd=2.5..3.3V only, so not fully I2C compliant = SMBus
is the best fit.
On Fri, 24 Apr 2009 07:52:54 +0100
Peter Robinson pbrobin...@gmail.com wrote:
Which kernel are you running?
The kernel is the rawhide variant 2.6.29.1 from about a week ago.
OK, that should rule out Hans's changes. In which case I'm totally
mystified...not a whole lot else has happened
[Sorry for the slow response, I am losing the battle with my inbox in a
spectacular way...]
I've been playing with rawhide on the XO this morning now that
I've finally got it booting of the SD easily and regularly. It
seems the camera doesn't work either in the record app or in
forget about it now.
I see no harm in having the driver check the device to ensure it's what
it thinks it is - we can probably afford the runtime overhead. But
whatever, I'm not that concerned; toss in an
Acked-by: Jonathan Corbet [EMAIL PROTECTED]
if you wish.
jon
Daniel Drake [EMAIL PROTECTED] wrote:
As far as we can see, this patch was never included in any OLPC builds.
However, we do ship some other delay improvements such as
http://dev.laptop.org/git?p=olpc-2.6;a=commitdiff;h=4ef53002
That patch is a bit of a sledgehammer approach; it really
Daniel Drake [EMAIL PROTECTED] wrote:
OK, thanks for the input. However there doesn't seem to be a timeout in
the case added by commit 6d77444aca29:
+ do {
+ prepare_to_wait(cam-smbus_wait, the_wait,
+ TASK_UNINTERRUPTIBLE);
+
Daniel Drake [EMAIL PROTECTED] wrote:
The hang occurs somewhere inside/below ov7670_write_array.
I'm just wondering if you have any ideas or suggestions here?
I've seen the bug report go by, but I'm only just today back in the
country after a couple of weeks on vacation. I'll look into it,
Walter Bender [EMAIL PROTECTED] wrote:
Second, regarding Microsoft, I agree that if it is to be an open
platform, it should be open to everyone, including Microsoft. That
said, it is somewhat revisionist to suggest that the SD card was added
on behalf of Microsoft
Such statements certainly
Arjun Sarwal [EMAIL PROTECTED] wrote:
(1) Am I poking in the right place ?
No, the PWC driver is not used on the XO. The OLPC camera driver driver
can be found in two pieces:
drivers/media/video/cafe_ccic.c (the controller driver)
drivers/media/vidoe/ov7670.c
David Woodhouse [EMAIL PROTECTED] wrote:
If we don't do it like that, we need to remember to chase our changes
upstream. Here's a quick summary of what looks like it needs to be
(cleaned up and) pushed upstream...
[...]
Jon Corbet:
Some cafe_ccic.c changes
Actually, I've sent all of
I can't speak for the OLPC kernel folks, but here's a few thoughts:
First off I noticed CONFIG_NO_HZ=y and CONFIG_HZ=100; is this a quirk of
the kernel's general configuration? As I understand, these options
should be mutually exclusive because CONFIG_HZ is a parameter of a
scheduler
in support for
VIDIOCGMBUF is actually feasible, though not entirely trivial. Far
better, if at all possible, would be to use the V4L2 API, which (like
high-definition TV and IPv6) is definitely the way of the future.
Someday.
jon
Jonathan Corbet / LWN.net / [EMAIL PROTECTED
Dan Williams [EMAIL PROTECTED] wrote:
So here you see that calling VIDIOC_S_FMT takes 3655992 microseconds,
which is a _really_ long time. Turns out that cafe_cam_configure() from
s_fmt_cap() takes 378 jiffies.
Trying to make this better was already on my list. The problem is that
the Cafe
[Hi, Jordan, from across the room]
They just talked about pagemap from Matt Mackall during an BoF at OLS.
This seems like something useful we can use to measure our memory
usage - in particular, it is screaming for tinderbox integration.. :)
http://lkml.org/lkml/2007/4/3/405
It's good
19 matches
Mail list logo
