Re: Next Familiar release...

> From: Robin Cutshaw <robin@interlabs.com>
> Date: Wed, 11 Jul 2001 09:52:41 -0400
> To: Jim Gettys <jg@pa.dec.com>, familiar@handhelds.org
> Subject: Re: [Familiar] Next Familiar release...
> -----
> On Tue, Jul 10, 2001 at 08:08:25AM -0700, Jim Gettys wrote:
> >
> > There are a number of open issues that still make setting a schedule in
> concrete
> > (to the extent this is ever possible in an open souce project) a bit
> difficult.
> >
> > These include:
> > 1) what kernel to use. Jamey's currently taking 2.4.6 for a spin: we'll
> > see. We'd like to get the fork used for the BackPAQ back into the
> mainstream.
> > 2.4.4 had a problem that prevented using the HP VGA card we'd like to get
> > fixed. Hopefully we'll know in the next couple days if 2.4.6 is a good
> > candidate. Tracking the mainstream is a long term necessity.
>
> Dual pcmcia sleeve support is a must. 2.4.6 would be nice.

Yup. 2.4.6 looks likely, with support for the dual.

>
> I've been flashing new kernels fairly often. Having to load them via the
> serial port from the boot loader is painful. Is there a reason why the
> kernels can't reside within the root file system? It would be really nice
> to remove the kernel partition and it's flashing requirements.

Yes: requires bootloader mods. Not clear when this will happen.

In the meanwhile, you can copy new kernels onto that partition directly
when running familiar.

>
> I really think that a dual boot (CE/familiar or intimate) would be helpful.
> It would allow more people to "play" with linux on their iPAQ. I would
> personally use this. CE has some interesting user interface designs. Most
> of the dual boot plusses on a PC would apply.

Would be nice: looks like some people are beginning to succeed. Time will
tell when we can pick this up.

>
> It would be nice to take a look at the O/S environment before release of 0.5.
> I add things like more, find, and passwd every time I reflash the O/S. A
> review of included apps would be good.

The base familiar should have as little as possible.

If there are missing tools you want, feel free to ipkg them up. It is easy
to do.

Also, a "program developer" ipkg metapackage to get a bunch of such tools
at once, particularly for those on 32 meg flash units, would be a big help.

>
> > 2) Power management got broken inadvertently: we need to get this fixed.
> > We have a clue: turning off the screen is causing audio to stop playing.
> > Clearly the screen power off code is messing with registers it isn't
> supposed
> > to; this may or may not be part of the power problem.
> >
>
> Yep, and my unit drains the batteries pretty quickly even when I put it to
> sleep.
>

As I said, we know things are broken. For example, turning off the screen
really shouldn't have anything to do with turning off audio, yet I've seen
this happen. This implies some registers are getting messed with that
shouldn't be, and may be the source of (some of) the power problems.
                                      - Jim
Received on Mon Jul 16 07:06:20 2001