0 Members and 2 Guests are viewing this topic.
lso, in other news, I2C is working on all touchpad platforms. Now we just need a driver for the touchpad. Just a heads up, since we're using the I2C bus now, we should define a I2C driver instead of a platform driver.
If you're using an initrd (which needs decompression as well), it doesn't make any difference.I'd say XZ, but do we really have to discuss about 0.5 MB (the kernel won't be much larger in the future)?Quote lso, in other news, I2C is working on all touchpad platforms. Now we just need a driver for the touchpad. Just a heads up, since we're using the I2C bus now, we should define a I2C driver instead of a platform driver.Can I do it?
I'll get cracking on the hardest device then - the NAND.
QuoteI'll get cracking on the hardest device then - the NAND.Yay! But we don't have any filesystem driver for it..But the driver shouldn't be TOO hard, the emulator source should be enough, maybe there's already a driver for our chip available?
The filesystem, we'll leave til later to solve. Perhaps the recently released nLaunch could help us here?
Edit: I've seen some interesting code hidden in the OS that formats the flash.Maybe there's some sort of data structure that we could modify to trick the OS into believing we have less NAND than we actually have and have it format the filesystem to only utilize that much. Under Linux, we could partition the NAND up and only use the portion that the Nspire OS doesn't use.
QuoteThe filesystem, we'll leave til later to solve. Perhaps the recently released nLaunch could help us here?Not nLaunch itself, but...QuoteEdit: I've seen some interesting code hidden in the OS that formats the flash.Maybe there's some sort of data structure that we could modify to trick the OS into believing we have less NAND than we actually have and have it format the filesystem to only utilize that much. Under Linux, we could partition the NAND up and only use the portion that the Nspire OS doesn't use.... in the community, we've known for nearly three years the boot2 1.4.1571 for Clickpad/Touchpad contains tons of debugging and testing code for Nucleus and its elements, especially filesystem operations The boot2 3.1.131 is smaller, and presumably doesn't contain as much.
BTW: Buildroot builds are working now.
I downloaded one, ran "tar -xvf xconfig.tar.bz2 -C ." and was surprised, MY PWD WAS "/"
Look what I found out: http://www.linux-mtd.infradead.org/nand-data/nanddata.htmlThe NAND is already actually supported by linux!I was a bit frustrated because of this silly synaptics_i2c polling too slow, so I did a bit of research.Edit: After reboot in linux the touchpad doesn't work anymore with nucleus, you have to reboot. But it doesn't boot anymore and you have to run NAND-Tests everytime you reboot in linux. I'll try disabling access with 1<<7 to 0x900B0018Edit2: The TOUCHPAD WORKS! I'll upload a video later/tomorrow
Vogtinator, you have royally screwed your desktop. You extracted an ARM linux install on top of your x86 linux root. You're lucky that it still boots, likely thanks to various configuration differences between the two.
The NAND chip itself is supported and always has been. But the NAND controller isn't
Nice, I look forward to seeing it
QuoteVogtinator, you have royally screwed your desktop. You extracted an ARM linux install on top of your x86 linux root. You're lucky that it still boots, likely thanks to various configuration differences between the two.Nope, it didn't boot. Had to restore the files from another laptop:"export list=`tar -tf xconfig.tar.bz2`; for i in $list; do echo $i; rm /mnt/$i; rsync -lptgoDvzP /media/$i /mnt/$i; done;"QuoteThe NAND chip itself is supported and always has been. But the NAND controller isn't Is it the same on all nspires?
QuoteNice, I look forward to seeing itHere you go:
Though, some one did ask about it in a mailing list in 2008 and probably succeeded in writing one.
It sounds like it isn't 'NAND' at all, as far as you're concerned. It'sa disk drive of some form. Usually these things present themselves asIDE, so you'd use the IDE driver. If it has its own 'special' interfacethen you probably want a dedicated block driver for it; nothing to dowith the MTD subsystem at all.
QuoteThough, some one did ask about it in a mailing list in 2008 and probably succeeded in writing one.I read:Code: [Select]It sounds like it isn't 'NAND' at all, as far as you're concerned. It'sa disk drive of some form. Usually these things present themselves asIDE, so you'd use the IDE driver. If it has its own 'special' interfacethen you probably want a dedicated block driver for it; nothing to dowith the MTD subsystem at all.WTF? Flash controller with IDE interface for ARM SoCs?
Author
Topic: Calling all Linux Kernel developers! (Read 392468 times)
