Hi Nikolaus,
The lcd fix is included in the patchminibookRV10 file.
http://projects.kwaak.net/twiki/pub/Epc700/KernelPort26Compiling/patchminibookRV10
It can be extracted from the patchminibookRV10 source for below two files.
jzlcd.c
jzlcd.h
Grt Ruben.
Subject: Re: [Mipsbook-devel] yaffs2
From: h...@computer.org
Date: Thu, 15 Jul 2010 20:22:22 +0200
CC: mipsbook-devel@linuxtogo.org
To: r_vi...@hotmail.com
Hi Ruben,
thanks for the update!
My activites for the kernel have been decelerated a little by other high
priority tasks...
Yes, the RTC did also no longer work on my newer mipsbook. Originally I had
worked on the older one which is now bricked. So I think there are two really
different models and they differ in PIC (powerdown) and RTC operation. And, the
newer one does not even have the RS232 interface connector...
What I am not sure is for which one the celinux skytone patches are for. Maybe,
the older one only :(
The LCD fix looks interesting. Do you have a diff just for that (that is why I
have moved to git because it is easy to inspect single changes)?
Best regards,
Nikolaus
Am 15.07.2010 um 19:48 schrieb Ruben Viets:
Hi Nikolaus,
I posted my latest stable working kernel 2.6.24.3 mods, copied some parts from
your letux-400 git and minibookv33 + additional ones.
- I did not use rtc fix because this doesn't seems to work, still use the old
driver.
- LCD seems to be fixed when adding some part from celinux24 skytone sources.
Based on linux-2.6.24.3.tar.bz2 + linux-2.6.24.3-jz-20100304.patch
Updates: patchminibookRV10 @
http://projects.kwaak.net/twiki/bin/view/Epc700/KernelPort26Compiling
Grt Ruben.
From: h...@computer.org
Subject: Re: [Mipsbook-devel] yaffs2
Date: Wed, 30 Jun 2010 08:11:04 +0200
To: r_vi...@hotmail.com
Hi Ruben,
Am 30.06.2010 um 06:36 schrieb Ruben Viets:
Hi Nikolaus,
I did not see the yaffs2 update/push on latest git resource yet.
It was indeed still missing. Don't know why. I have now double-checked...
PIC update is interesting. Stuck of kernel related to MMC and IRQ, could this
be simular issue we have with sound ?
Could be!
Just some ideas, change the order of the gpio init in board-minipc.c, change
the compiling order of the PIC driver to be compiled before MMC.
What I suspect is either a general bug in the interrupt handling (maybe, the
interrupt numbers are simply being mixed up) or in the board initialization
(interrrupts can occur before the handlers are properly initialized.
At least two hypotheses for further study :)
BR,
Nikolaus
Grt Ruben.
> Subject: Re: [Mipsbook-devel] yaffs2
> From: h...@computer.org
> Date: Mon, 28 Jun 2010 09:36:50 +0200
> CC: mipsbook-devel@linuxtogo.org
> To: r_vi...@hotmail.com
>
> Hi Ruben,
> I have now pushed the yaffs2 changes so you should see them and no longer get
> segfaults.
>
> What I also have tried is to improve the PIC control code (not yet
> committed). It appears that I have two different hardware models. One did
> (because it is now bricked) respond to the code in GIT, while the other just
> prints pic-shutdown but the kernel continues to run. So I don't know if power
> is controlled on this model through GPIO 69 or I2C or even both. Both models
> must have different PIC firmware since the older model just switches the
> screen on (which shows random pixels), then needs one second until the SYNC
> comes. The newer one keeps the screen dark for 1 second...
>
> Finally, I have tried to work on the PIC interrupt (to teach the power button
> to send ctl-alt-del). But there I have a strange situation. As soon as I
> register my IRQ for GPIO 65 the kernel no longer boots but hangs with an
> uninitialized IRQ for GPIO 64. This is the MMC card detect intererupt.
>
> What I don't understand: why is this INT occurring, but uninitialized? And,
> why only if I request_irq(IRQ_GPIO_0 + 65, ...)?
>
> Well, it may be a race condition combined with the initialization of the
> whole interrupt system. If the kernel does not respond to any intererupt
> before the first request_irq() is done, and the card detect line is already
> active (because I boot from SD), this could explain the situation.
>
> Best regards,
> NIkolaus
>
>
> Am 20.06.2010 um 13:22 schrieb Ruben Viets:
>
> > Hi Nikolaus,
> >
> > Downloaded the latest git sources. git clone
> > git://git.goldelico.com/letux-400.git
> >
> > Two issues, may need additional fix or upload of your local patches:
> > - issue with nand mounting. Showing errors on yaffs2 tragedy.. cause kernel
> > segfault and stuck
> > - The key's to startup from different boot don't work, alway's rooted from
> > /dev/mtdblock4.
> >
> > Grt Ruben.
> >
> > From: r_vi...@hotmail.com
> > To: h...@computer.org
> > Date: Sat, 19 Jun 2010 10:10:11 +0000
> > CC: mipsbook-devel@linuxtogo.org
> > Subject: Re: [Mipsbook-devel] yaffs2
> >
> > Hi Nikolaus,
> >
> > I have simular result. Used df to see the size and available space on all
> > partitions.
> >
> > - It looks like the /dev/mtdblock3 is in use by jffs2 blocks.
> > dmesg shows some prioritised blocks when mounting as yaffs2. So better to
> > mount as jffs2 I think.
> >
> > So far this kernel 2.6.24.3 and the updated sources are very usable now. ;-)
> >
> > Grt Ruben.
> >
> >
> > > Subject: Re: [Mipsbook-devel] yaffs2
> > > From: h...@computer.org
> > > Date: Wed, 16 Jun 2010 08:44:33 +0200
> > > CC: r_vi...@hotmail.com; mipsbook-devel@linuxtogo.org
> > > To: h...@computer.org
> > >
> > >
> > > Am 16.06.2010 um 08:31 schrieb Dr. H. Nikolaus Schaller:
> > >
> > > >
> > > > Am 15.06.2010 um 20:34 schrieb Ruben Viets:
> > > >
> > > >> Hi Nikolaus,
> > > >>
> > > >> You already have all sources if you tar xvjf the linux-2.6.24.3 and
> > > >> afterwards patch -p1 < patch20080530 + patchv33_withoutyaffs2
> > > >
> > > > Ok, this was quite easy.
> > > >
> > > > I did not find many differnces:
> > > >
> > > > include/mtd/mtd-abi.h -- different size for oob fields (which may be
> > > > the issue)
> > > > fs-fs-writeback.c -- different strategy for locking
> > > > fs/mpage.c -- "It seems that there is a IO coherent bug in
> > > > generic_file_mmap()"
> > > > fs/yaffs/* -- about 50% of the files differ
> > > >
> > > >
> > > >>
> > > >> Don't need to tar and send my files then. Question is if the below
> > > >> dirs you mention are enough. You may need additional files.
> > > >> So better start from scratch in a different dir and do a diff with
> > > >> your letux-400 development directory.
> > > >>
> > > >> My latest config (CONFIG_RV9) is located at
> > > >> http://projects.kwaak.net/twiki/pub/Epc700/KernelPort26Compiling/CONFIG_RV9
> > > >
> > > > Here I did not have CONFIG_MTD_SW_HM_ECC set and none of the VERIFY
> > > > options
> > > >
> > > > Now it *appears* to work. There are still some strange messages like
> > > > "Freechunks verification failure" but I did not do a flash_eraseall - I
> > > > just tried to continue to use the file system created with the broken
> > > > yaffs2.
> > >
> > > Ok, I have erased the minifs partition and mounted as yaffs2. The message
> > > has disappeared.
> > >
> > > But there is a mismatch between used/available blocks and what I see as
> > > files (an empty lost+found directory). And 'du' reports 40% used.
> > >
> > > When initializing as jffs2 I get 8% used and a completely empty device.
> > >
> > > Or is yaffs inappropriate for small NAND partitions?
> > >
> > > Nikolaus
> >
> > New Windows 7: Simplify what you do everyday. Find the right PC for you.
> > New Windows 7: Simplify what you do everyday. Find the right PC for you.
>
Express yourself instantly with MSN Messenger! MSN Messenger
New Windows 7: Simplify what you do everyday. Find the right PC for you.
_________________________________________________________________
New Windows 7: Find the right PC for you. Learn more.
http://windows.microsoft.com/shop_______________________________________________
Mipsbook-devel mailing list
Mipsbook-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/mipsbook-devel
