OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

> Some News: Kernel 2.6, Arcdisk Support
guylhem
post Jul 12 2005, 12:04 PM
Post #1





Group: Members
Posts: 577
Joined: 17-March 04
Member No.: 2,365



Hello

Thanks to Bruno kind help, I'm working on pdaxrom and debian support using a 40 Gb arcdisk. Ideally, I will follow the release map and offer a big choice of interfaces. [If you guys want a 4 Gb CF support, tell me]

However, I just discovered that for some reason, my kernel had problems with the arcdisk (usb storage too old certainly) - a new release is planned. Moreover, it seems to hang on my good old audiovox at startup for no reason.

Maybe it's time to move to a 2.6 ? I will try and test everything to make sure it will work at least as good. Stay tuned!

Guylhem
Go to the top of the page
 
+Quote Post
 
Start new topic
Replies
guylhem
post Jul 13 2005, 02:50 PM
Post #2





Group: Members
Posts: 577
Joined: 17-March 04
Member No.: 2,365



I'm not dead- just too busy in the ER !

ken, I don't plan to stop the rom - only sample the 2.6 kernel to consider whether it is stable enough for distribution and use, and porting features.

gfdsa - I have no list of known bugs. I have to try it myself. You can test OZ and tell me :-)

"guylhem rom" is going to become more a distribution than everything at once. There are specific things I want to improve: speed, hackability, compatibility - triple binds mutually exclusive - comes what may :-)

Actually I'm very interested in the suspend/resume time and the boottime. I want it to be blazing fast.

To do this, I did cut the kernel messages, and I'll certainly cut the logo. dmesg is still there- messages are just logged to ttyS0 instead of the console by default. I enabled sysv status report (ex: Checking filesystem [OK]) OTOH because it was important to find which part was hanging when a problem occured, even if it display stuff and therefore may add some delay. I am also adding a pretty issue screen, because of the hackability.

See my plans? It's mostly a personal effort- I want it that way because I think it is the right way, but there's no special goal- only to have the best free software distribution for a handheld.

BTW Last week in Dijon I saw some openbsd people working on a OpenBSD over C3100 project, which I promised to give a hand at least on the kernel part (even without the hardware - they had power management problem). I will try to interest them on the boot process, to replace the old bsd or sysv init by something more suitable to handhelds. It could be based on something much more efficent and modern like http://www.atnf.csiro.au/people/rgooch/linux/boot-scripts/

Anyway we'll see... I'll try to make everything fit on the flash, having the various systems on microdrives or 40 Gb usb storage. adf - maybe your pdaxrom system (saw your instructions on the 6000 forum) could be included? All it needs is to work with guylhem rom.
Go to the top of the page
 
+Quote Post
ken
post Jul 20 2005, 01:04 PM
Post #3





Group: Members
Posts: 274
Joined: 17-October 04
Member No.: 5,063



QUOTE(guylhem @ Jul 13 2005, 12:50 PM)
ken, I don't plan to stop the rom - only sample the 2.6 kernel to consider whether it is stable enough for distribution and use, and porting features.

ok, that's good to know.

It's understandable that you're busy and all. That being the case, I was wondering if you would consider a few thoughts ...

The guylhem rom is an ambitious but doable project, certainly something that a number of us want to see completed. The distribution however, has many aspects to it, many pieces, many parts that need to fit together.

That being the case, perhaps it would be useful to break them up into smaller bite sized portions?

At the very least, it would help in the troubleshooting process, to see if there is a piece that's inadvertantly affecting other parts? You've already gone far ahead of many of us, and there's little we can do to help figure out what's going on.

Your forums gives hints as to the directions you've taken, but I fear, not enough for someone like myself to get enough of a big picture.

Perhaps starting with something like:

1) tetsu's kernel (for the 6K it's up to 16a). That would provide people with ?. That also may possibly have other inclusions of things you want to do. That could be a starting point. He has for example, included bluetooth. Of course if you feel that using his kernel would have a number of disadvantages (which you'd know and I'd have no clue on), then of course, this would be a bad idea.

2) meanie's patches for usb perhaps?

3) a fast SDL - this is what attracted people to your rom in the first place - the idea that they could add a touch of speed to the 6K.

4) ability to have more than just 25%, 50%, 75% brightness

That being said, I have the feeling that you can already see how each thing would fit together, from just the kernel patches to the full blown guylhem distribution?

At least this way you could take more time to figure out where things are breaking?
QUOTE
There are specific things I want to improve: speed, hackability, compatibility - triple binds mutually exclusive - comes what may :-)

I have no disagreements there. Merely concerned that it may lose its momentum.

QUOTE
Actually I'm very interested in the suspend/resume time and the boottime. I want it to be blazing fast.

boot time is nice, but once it's booted, it's a not a biggie. suspect/resume, yes, I can see that. I suspect that's a long term goal though.
QUOTE
To do this, I did cut the kernel messages, and I'll certainly cut the logo. dmesg is still there- messages are just logged to ttyS0 instead of the console by default. I enabled sysv status report (ex: Checking filesystem [OK]) OTOH because it was important to find which part was hanging when a problem occured, even if it display stuff and therefore may add some delay. I am also adding a pretty issue screen, because of the hackability.

This part can be what I mentioned above. Tiny pieces that provide functionality, little modules that allow you to hack a part of the system, guaranteed to work.

QUOTE
suitable to handhelds. It could be based on something much more efficent and modern like

heh ... it's all good. The downside of course is your time gets spread further apart!

QUOTE
systems on microdrives or 40 Gb usb storage. adf - maybe your pdaxrom system (saw your instructions on the 6000 forum) could be included? All it needs is to work with guylhem rom.

I'm willing to help in any way I can. To that extent, I've been working on a page:

http://www.oesf.org/index.php?title=Applic...6000L/Sharp_ROM

This is geared of course to what we discussed, being that compatibility to the Sharp ROM is important. I'm also afraid that adding in gcc3 might break things, but you'd know better than myself whether it would or not.

Let me know how I can help.

btw, the article here: http://www.externe.net/zaurus/modules.php?...order=0&thold=0

that talks about a website is now located here:

http://home.mchsi.com/~cmisip/zaurus.htm
Go to the top of the page
 
+Quote Post

Posts in this topic


Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 21st September 2014 - 06:14 PM