Devel Digest, Vol 10, Issue 39
jk
jk at epigon.co.in
Sun Dec 31 06:03:51 EST 2006
Dear OLPC team,
We wish you all very best 2007.
Kind Regards
jk
>From Bangalore, India
http://www.epigon.in/
----- Original Message -----
From: <devel-request at laptop.org>
To: <devel at laptop.org>
Sent: Sunday, December 31, 2006 2:48 PM
Subject: Devel Digest, Vol 10, Issue 39
> Send Devel mailing list submissions to
> devel at laptop.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman.laptop.org/mailman/listinfo/devel
> or, via email, send a message with subject or body 'help' to
> devel-request at laptop.org
>
> You can reach the person managing the list at
> devel-owner at laptop.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Devel digest..."
>
>
> Today's Topics:
>
> 1. Re: OLPC Laptop - an open source substandard ? (Alex Gibson)
> 2. package system for the OLPC (Ian C.)
> 3. Re: OLPC Laptop - an open source substandard ? ( ticket #46 )
> (Alex Gibson)
> 4. Re: OLPC Laptop - an open source substandard ? (Jim Gettys)
> 5. Re: OLPC Laptop - an open source substandard ? (Alex Gibson)
> 6. Re: [PATCH] Open Firmware device tree virtual filesystem
> (David Miller)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 31 Dec 2006 14:13:34 +1100
> From: Alex Gibson <agibson at eng.uts.edu.au>
> Subject: Re: OLPC Laptop - an open source substandard ?
> To: devel at laptop.org
> Message-ID: <45972ADE.9000706 at eng.uts.edu.au>
> Content-Type: text/plain; charset="utf-8"
>
> Ivan KrstiÄ? wrote:
> > Michail Bletsas wrote:
> >
> >> The issue is that we need working code now and we have to rely on
> >> whatever RTOS people that can deliver code under hard deadlines feel
> >> comfortable working with.
> >>
> >
> > Right, but this is a different discussion -- as per ticket #46
> > (http://dev.laptop.org/ticket/46), about getting the Marvell code under
> > NDA to someone for porting.
> >
> > Previously, there was no known suitable (free) porting target. Now eCOS
> > has emerged as one.
> >
> >
>
> There are a few
>
> ecos - ecos.sourceware.org
> modified gpl http://ecos.sourceware.org/license-overview.html
>
> freertos - www.freertos.org
> modified gpl
>
> tinyos - http://www.freertos.org/a00114.html
> license ? http://www.tinyos.net/faq.html#SEC-17
>
> Any other suitable open source rtos ?
>
> Do the licenses linked to above, meet the requirements ?
>
> Michail, what are the deadlines ?
>
> I know the group head of ICT Engineering (Information and Communications
> Technology)
> has had a talk with the local Marvell rep on getting an NDA signed.
>
> I'll have a talk with him at the open day on the 3rd and see if we can
> get this sped up.
> Unfortunately a lot of companies here shutdown for summer holidays until
> the end of janurary , so
> we'll have to see what we can do.
> (summer school holidays 13 dec - 3rd feb)
> (uni holidays end of nov - march - full three months for students)
>
> I'm an interested in having a go but can not commit to any deadlines as
> am working
> full time for a research lab/company until the end of January
> on license plate recognition systems and deployments.
>
> May be better placed to assist with testing of a driver
> as we have a full communications testing lab which is not currently being
> utilised. Have equipment for up to 50GHz.
>
> Has anyone started looking at repeaters or message box storage or
> internet gateways yet ?
>
>
> Alex Gibson
>
> Technical Officer
> Network Sensor Technologies Laboratory
> University of Technology Sydney
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
http://mailman.laptop.org/pipermail/devel/attachments/20061231/61f8b681/atta
chment-0001.html
>
> ------------------------------
>
> Message: 2
> Date: Sat, 30 Dec 2006 19:28:58 -0800
> From: "Ian C." <inchosting at gmail.com>
> Subject: package system for the OLPC
> To: devel at laptop.org
> Message-ID: <45972E7A.7010009 at gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> hello
> I have some software you may be interested in; it is a package
> management system coded in python.
> The project is called cap-python, it is a pretty basic system.
> It is coded in a modular fashion so it can be tied into many different
> interfaces and/or
> an installer for the OS. Currently there is a beta version of a pygtk
> interface for cap-python,
> a screen shot of it is available at
> http://arcanelinux.org/screenshots/cap-pygtk.jpg .
> It has object oriented/modular repo database access code, so it can
> access a variety of database formats both
> local and remote while leaving the possibility for more. It currently by
> default ties into the online
> capsule repository web service. The online tools for cap-python can be
> seen at http://caps.arcanelinux.org/ . Also the latest documentation
> that was written for it can be found at
> http://inc-omplete.org/wiki/index.php/Capsules/Documentation .
> <http://inc-omplete.org/wiki/index.php/Capsules/Documentation>
> Thank you for your time, and please let us know if you are interested.
> --Ian "Inc" C.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
http://mailman.laptop.org/pipermail/devel/attachments/20061230/16f49667/atta
chment-0001.html
>
> ------------------------------
>
> Message: 3
> Date: Sun, 31 Dec 2006 14:27:29 +1100
> From: Alex Gibson <agibson at eng.uts.edu.au>
> Subject: Re: OLPC Laptop - an open source substandard ? ( ticket #46 )
> To: devel at laptop.org
> Message-ID: <45972E21.9060909 at eng.uts.edu.au>
> Content-Type: text/plain; charset=ISO-8859-15
>
> Andi wrote:
> > Hi Jim, Hi list,
> >
> > Jim Gettys wrote:
> >> Unless that investment can be done in parallel, this change translates
> >> into delay and cost. Right now, there are only one set of people
> >> familiar with the mesh code, working under a tight deadline. We're not
> >> about to tell them to delay the overall project by switching horses in
> >> midstream.
> >>
> >> So to break the conundrum there also have to be people willing to
> >> actually do the work, as the primary firmware team is working on
getting
> >> us code we can use and deploy.
> > ...
> >> As in the base system BIOS/firmware situation, the right way to look at
> >> this is we know the desired/needed end-state, and to take steps toward
> >> that state as time and resources permit.
> >
> > That's good news.
> > Basically you say that you will *support* a parallel development, if
> > there are people willing to do a parallel development.
> > OK.
> > What's needed to start:
> > - a cheap and easy to get development environment:
> > Since a BTest-1 Systems is still a hard to get thing...
> > In what cheap device, *sold* *worldwide*, is the Marvell Libertas
> > 88W8388 chip in a to the Gen1-System compatible manner build in ?
> > Candidates:
> > - Xbox 360 WifiAdapter http://wiki.free60.org/WifiAdapter
> > Start at 65 EUR
> > Could someone ask Marvell kindly about that please ?
> >
> > If we have OLPC Gen1-System compatible development hardware we could
> > evaluate the Marvell RTOS alternatives http://ecos.sourceware.org/ and
> > http://www.tinyos.net/
> >
> >
> > Andi
>
> Its a pity the gumstix.com guys used the 88W8385
> as their wifi stix board would have been perfect
> http://gumstix.com/store/catalog/product_info.php?products_id=172
> (I have a couple on my desk)
>
> There is an olsr package now available in their standard buildroot.
>
> But I don't think they do yet have that opensource driver they mention.
> They ran into the same problem with the firmware.
>
> May be worth while for someone to have a chat with them.
>
>
> Alex
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 30 Dec 2006 23:20:54 -0500
> From: Jim Gettys <jg at laptop.org>
> Subject: Re: OLPC Laptop - an open source substandard ?
> To: Alex Gibson <agibson at eng.uts.edu.au>
> Cc: devel at laptop.org
> Message-ID: <1167538854.4868.317.camel at localhost>
> Content-Type: text/plain
>
> On Sun, 2006-12-31 at 14:13 +1100, Alex Gibson wrote:
>
> >
> > Michail, what are the deadlines ?
> >
>
> Our current deadlines are irrelevant to the discussion. We are not
> going to divert the current development to a different embedded system
> code base until and unless the alternative is equally functional. In
> this sense, there is no deadline. The networking is fundamental to the
> project.
>
> Different firmware can be deployed at essentially arbitrary future
> dates; obviously those will fold into future release schedules, but this
> is far enough out that the discussion of deadlines is academic.
> Best Regards,
> - Jim
>
>
> --
> Jim Gettys
> One Laptop Per Child
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 29 Dec 2006 12:46:40 +1100
> From: Alex Gibson <agibson at eng.uts.edu.au>
> Subject: Re: OLPC Laptop - an open source substandard ?
> To: devel at laptop.org
> Message-ID: <45947380.6010102 at eng.uts.edu.au>
> Content-Type: text/plain; charset="utf-8"
>
> Ivan KrstiÄ? wrote:
> > Gabor Dolla wrote:
> >
> >> - The goal to have an open source solution. If the code will be free
and
> >> available what is the purpose of NDA ?
> >>
> >
> > The meshing code is inextricable from the RTOS currently used, which is
> > commercial and proprietary. The RTOS is thus delivered as part of the
> > meshing code for porting, and protecting the RTOS requires an NDA.
> >
>
> The rtos is threadx ?
> >
> >> - Marvell would hand over the full specs of the chip including the
radio
> >> part ? AFAIK usually the radio part is kept as a secret to make
> >> regulators happy,,, Or the radio part would be in binary format ?
> >>
> >
> > Still being discussed.
> >
> >
> >> - 802.11 b/g is also implemented in software as in recent prism54 chips
> >> (soft MAC)? The open source solutions should cover that part too ?
> >>
> >
> > Not sure about this bit. Michalis?
> >
> >
> >> - An underlying OS (ticket suggest TinyOS) is really needed ?
> >>
> >
> > Yes. I've recently received the suggestion that eCos, which is GPL'd,
> > can be used for this purpose.
> >
> There is also free rtos - freertos.org
>
> Which has a port for arm9 (ports for arm7 as well) already like ecos
> does but the footprint is a bit smaller
> than ecos. Gives the choice of pre-emptive and co-operative real time
> kernels
>
> Its available under a modified gpl
> http://www.freertos.org/a00114.html
>
> Alex
> >
> >> - 802.11s or batman is preferred ?
> >>
> >
> > We've chosen to go with 802.11s.
> >
> >
> >> - 802.11i is in the scope ?
> >>
> >
> > Not initially, as far as I know.
> >
> >
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
http://mailman.laptop.org/pipermail/devel/attachments/20061229/ead82a9d/atta
chment.html
>
> ------------------------------
>
> Message: 6
> Date: Sat, 30 Dec 2006 21:19:41 -0800 (PST)
> From: David Miller <davem at davemloft.net>
> Subject: Re: [PATCH] Open Firmware device tree virtual filesystem
> To: wmb at firmworks.com
> Cc: linux-kernel at vger.kernel.org, devel at laptop.org
> Message-ID: <20061230.211941.74748799.davem at davemloft.net>
> Content-Type: Text/Plain; charset=us-ascii
>
> From: Mitch Bradley <wmb at firmworks.com>
> Date: Sat, 30 Dec 2006 15:38:46 -1000
>
> > Request for comments.
> >
> > This patch creates a virtual filesystem that represents an Open Firmware
> > device tree. It has been tested on an OLPC x86 system, but the code is
> > not processor-specific (apart from its current location under
arch/i386).
> >
> > It requires an Open Firmware implementation that can stay resident
during
> > Linux startup.
> >
> > It is similar in some respect to fs/proc/proc_devtree.c , but does not
> > use procfs, nor does it require an intermediate layer of code to
> > create a flattened representation of the device tree.
> >
> > The patch applies cleanly against the current version of
> > git://dev.laptop.org/olpc-2.6 . (commit
5b9429be6056864b938ff6f39e5df3cecbbfcf4b).
> >
> > Please cc me (Mitch Bradley <wmb at firmworks.com>) on comments.
>
> Can we please not have N different interfaces to the open-firmware
> calls so that perhaps powerpc and Sparc have a chance of using this
> code too?
>
> On sparc and powerpc, we even build an in-kernel data structure of the
> entire open-firmware device tree that code like your's could use if
> you make a simple setup layer for i386 as well. We have interfaces for
> modifying property values at run time too.
>
> I would strongly suggest looking at things like
> arch/{sparc,sparc64,powerpc}/kernel/prom.c and
> include/asm-{sparc,sparc64,powerpc}/prom.h and
> arch/{sparc,sparc64,powerpc}/kernel/of_device.c and
> include/asm-{sparc,sparc64,powerpc}/of_device.h
> since we've already invested a lot of thought and
> infrastructure into providing interfaces to this information
> on powerpc and the two sparc platforms.
>
> Thanks.
>
>
> ------------------------------
>
> _______________________________________________
> Devel mailing list
> Devel at laptop.org
> http://mailman.laptop.org/mailman/listinfo/devel
>
>
> End of Devel Digest, Vol 10, Issue 39
> *************************************
>
More information about the Devel
mailing list