Pavel Machek wrote:
> > Alternatively, it is possible to write a driver. It is just one byte
> > write and one byte read via I2C.
>
> Do you know what byte it is? That sounds easy enough...
Yes, it should be easy driver. One byte address and then one byte write
or one byte read.
See the datashe
On Sun 2010-03-21 22:42:33, Stanislav Brabec wrote:
> Pavel Machek píše v Ne 21. 03. 2010 v 21:43 +0100:
> > On Fri 2010-03-12 10:07:04, Stanislav Brabec wrote:
>
> > > > > Good tip. It seems that nobody ported driver for the voltage control
> > > > > chip ISL6271 from 2.4 kernel, and bootloader p
Pavel Machek píše v Ne 21. 03. 2010 v 21:43 +0100:
> On Fri 2010-03-12 10:07:04, Stanislav Brabec wrote:
> > > > Good tip. It seems that nobody ported driver for the voltage control
> > > > chip ISL6271 from 2.4 kernel, and bootloader probably does not set
> > > > correct values.
>
> Are we sure
On Fri 2010-03-12 10:07:04, Stanislav Brabec wrote:
> Andy Green wrote:
> > On 03/11/10 15:42, Somebody in the thread at some point said:
> > > Andy Green wrote:
> > >
> > >> I saw very similar failures for a long time on our iMX31 based device.
> > >> Eventually I found a Freescale errata where t
On Mon 2010-03-08 12:48:36, Stanislav Brabec wrote:
> Cyril Hrubis wrote:
>
> > Well I've seen empty lines when editing file with vim
>
> And I have seen:
>
> - Unreproducible SIGSEGV of gcc (while Wi-Fi connection over CF card was
> running).
> - Unreproducible SIGSEGV of opkg (downloading vi
On 03/12/10 10:43, Somebody in the thread at some point said:
Andy Green wrote:
In that case is the PXA CF driver PIO? Then it can be the same load on
Vcore issue in disguise.
There is a proprietary ASIC chip (Sharp Scoop) that handles CF and HDD
access (and also several additional GPIOs):
h
Andy Green wrote:
> In that case is the PXA CF driver PIO? Then it can be the same load on
> Vcore issue in disguise.
There is a proprietary ASIC chip (Sharp Scoop) that handles CF and HDD
access (and also several additional GPIOs):
http://www.penguin.cz/~utx/zaurus/datasheets/ASIC_S1L50752B26B
On 03/12/10 09:07, Somebody in the thread at some point said:
Unless there's more to it in the way the zaurus using it that regulator
isn't programmable digitally.
OOPS, I made a mistake and linked ISL6721 instead of ISL6271 there.
Now it is fixed:
http://www.penguin.cz/~utx/zaurus/datasheets/
Andy Green wrote:
> On 03/11/10 15:42, Somebody in the thread at some point said:
> > Andy Green wrote:
> >
> >> I saw very similar failures for a long time on our iMX31 based device.
> >> Eventually I found a Freescale errata where the RAM inside the USB2
> >> macrocell started to make single bit
On 03/11/10 15:42, Somebody in the thread at some point said:
Andy Green wrote:
I saw very similar failures for a long time on our iMX31 based device.
Eventually I found a Freescale errata where the RAM inside the USB2
macrocell started to make single bit errors below 1.38V Vcore; ours was
1.4V
On 03/08/10 08:25, Somebody in the thread at some point said:
Hi!
dmesg would not be useful, it usually hits user programs. Like... mutt
suddenly displaying , instead of - in the header. Program failing to
start because function printg is not found (it was not exactly
printf->printg, I don't re
Andy Green wrote:
> I saw very similar failures for a long time on our iMX31 based device.
> Eventually I found a Freescale errata where the RAM inside the USB2
> macrocell started to make single bit errors below 1.38V Vcore; ours was
> 1.4V at that time but dipped on CPU load.
Good tip. It se
Hi!
> Is this display rotated by 90 degrees?
Yes it is.
> If so, they're actually horizontal lines as far as the display scanning
> is concerned - and that tends to suggest that there's insufficient system
> bus bandwidth for all the activity taking place, and the LCD controller
> is being starve
On Mon, Mar 08, 2010 at 01:16:35PM +0100, Cyril Hrubis wrote:
> Hi!
> > - And I see display noise while CF Wi-Fi card is active.
>
> Forgotten about this one. See for yourself, notice short black vertical lines
> flashing randomly.
I haven't looked at the video.
Is this display rotated by 90 deg
Hi!
> - And I see display noise while CF Wi-Fi card is active.
Forgotten about this one. See for yourself, notice short black vertical lines
flashing randomly.
http://atrey.karlin.mff.cuni.cz/~metan/outgoing/zaurus_sickness.mpg
--
metan
___
Zaurus-de
Cyril Hrubis wrote:
> Well I've seen empty lines when editing file with vim
And I have seen:
- Unreproducible SIGSEGV of gcc (while Wi-Fi connection over CF card was
running).
- Unreproducible SIGSEGV of opkg (downloading via Wi-Fi connection over
CF card).
- Unreproducible SIGSEGV of rm (ca
Hi!
> dmesg would not be useful, it usually hits user programs. Like... mutt
> suddenly displaying , instead of - in the header. Program failing to
> start because function printg is not found (it was not exactly
> printf->printg, I don't remember exact symbol), ping complaining
> about discarding
> On Sat, Mar 6, 2010 at 5:27 AM, Pavel Machek wrote:
> > Hi!
> >
> > I'm getting way too many bit errors on spitz, with various
> > kernels.
> >
> > It may be tied to network usage (bluetooth or wifi?). It happens even
> > on AC power.
>
> Pavel,
>
> What kind of bit errors? I'm not using any n
On Sat, Mar 6, 2010 at 5:27 AM, Pavel Machek wrote:
> Hi!
>
> I'm getting way too many bit errors on spitz, with various
> kernels.
>
> It may be tied to network usage (bluetooth or wifi?). It happens even
> on AC power.
Pavel,
What kind of bit errors? I'm not using any network here on my spitz
Hi!
I'm getting way too many bit errors on spitz, with various
kernels.
It may be tied to network usage (bluetooth or wifi?). It happens even
on AC power.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky,
20 matches
Mail list logo
