#155: PCI Pin A needs to be routed to a real interrupt
--+-
Reporter: JordanCrouse |Owner: rsmith
Type: defect| Status: new
Priority: blocker |Milestone: BTest-1
Component: li
#155: PCI Pin A needs to be routed to a real interrupt
--+-
Reporter: JordanCrouse |Owner: rsmith
Type: defect| Status: new
Priority: blocker |Milestone: BTest-1
Component: li
#185: Need better SPI FLASH recovery procedure
---+
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: task | Status: new
Priority: high | Milestone:
On Fri, 13 Oct 2006 08:26:07 -
"Zarro Boogs per Child" <[EMAIL PROTECTED]> wrote:
> That would get it down to about a minute, plus the time it
> takes for the serial downloader to do the rest (about half a minute).
>
> If we needed to, we could go even faster. The serial line speed
> limi
On Thu, 12 Oct 2006, Stephen Hemminger wrote:
> Is there any interest in working out some config options to downsize the Linux
> TCP stack by eliminating the stuff that doesn't make sense in a simpler
> environment?
>
> Lots of the sysctl parameters, congestion control options, route cache, all
On Wed, Oct 11, 2006 at 09:03:18PM -1000, Mitch Bradley wrote:
> An Open Firmware image for OLPC is available for testing. See
> http://firmworks.com/linux/OFWtest.html for complete instructions.
I've tried ofw-061011-1916 on both of my A-Test boards, and it worked
fantastically. It was very qu
James Cameron wrote:
On Wed, Oct 11, 2006 at 09:03:18PM -1000, Mitch Bradley wrote:
An Open Firmware image for OLPC is available for testing. See
http://firmworks.com/linux/OFWtest.html for complete instructions.
I've tried ofw-061011-1916 on both of my A-Test boards, and it worked
fa
When we say LinuxBIOS in the context of OLPC, we have generally meant
LinuxBIOS and some boot loader payload. The boot loader is that program
that can load the system into memory; a boot loader needs to be able to
talk to the hardware, and implement file systems to be able to read the
kernel image
Speaking as the guy who really likes linux as bootloader, and will
continue to use it for many platforms as I have for 6 years now, I have
really thought a lot about this change from Linux to OFW, and I'm good
with it.
I still am not sure I'm sold on all the merits (we've seen here that
once
On Fri, 2006-10-13 at 12:34 -0600, Ronald G Minnich wrote:
[...]
>
> I think that we, as a group, should now go to the Linux kernel guys and
> ask them to please, pretty please, put OFW parsing into the PC side of
> the house -- it's in the PPC and Sun side, has been for years, no reason
> not
Yeah, I like LAB too. Let no one think I don't.
On Fri, 2006-10-13 at 12:34 -0600, Ronald G Minnich wrote:
> Speaking as the guy who really likes linux as bootloader, and will
> continue to use it for many platforms as I have for 6 years now, I have
> really thought a lot about this change from
ron wrote:
>
>I think that we, as a group, should now go to the Linux kernel guys and
>ask them to please, pretty please, put OFW parsing into the PC side of
>the house -- it's in the PPC and Sun side, has been for years, no reason
>not to have it in the PC side. Stefan and I have asked for this
Mitch correctly points out (in private mail) that OFW was always an open
standard: the specs were open and multiple implementations existed.
So I'm happy to eat crow. As opposed to OpenVMS, (a true misnomer if
ever I saw one, and I worked for that company when that screamer was
done), OFW was a
I tried to tear the ofw image apart, and if the "files" were compressed with
lzma instead of gzip, it all fits in around 220 kbyte, which means that a LinuxBIOS with
ofw could fit into
any commodety 256k BIOS used in ordenary PC's - so this could
really be a lifter for LinuxBIOS aswell.
I
FirmWorks has done many OFW implementations in 256K, even with the
outstanding compression available with LZMA.
I meant to say "without", not "with".
D'oh!
___
Devel mailing list
Devel@laptop.org
http://mailman.laptop.org/mailman/listinfo/devel
We should have the OFW building tools available in a public place within
a few weeks. At that point it would be really cool if someone would
undertake the conversion to LZMA.
___
Devel mailing list
Devel@laptop.org
http://mailman.laptop.org/mailman/l
Mitch Bradley wrote:
We should have the OFW building tools available in a public place within
a few weeks. At that point it would be really cool if someone would
undertake the conversion to LZMA.
why not just LZMA the whole image? It's running as a single linuxbios
payload right? I am hoping
Ronald G Minnich wrote:
Mitch Bradley wrote:
We should have the OFW building tools available in a public place
within a few weeks. At that point it would be really cool if someone
would undertake the conversion to LZMA.
why not just LZMA the whole image?
That makes it a little smaller but no
>> why not just LZMA the whole image?
ofw is like a "tar" of mostly gzipped files
ofw as distributed here -> 338 kB
that image throught lzma -> 300 kB
compress idividual files -> 225 kB
It could make sense to include VSA and .. in this kind of
tar like a minifilesystem to avoid duplication of
Peter Lorenzen wrote:
>>> why not just LZMA the whole image?
>
> ofw is like a "tar" of mostly gzipped files
>
> ofw as distributed here -> 338 kB
> that image throught lzma -> 300 kB
> compress idividual files -> 225 kB
>
> It could make sense to include VSA and .. in this kind of
> tar like a
Carl-Daniel Hailfinger wrote:
Peter Lorenzen wrote:
why not just LZMA the whole image?
ofw is like a "tar" of mostly gzipped files
ofw as distributed here -> 338 kB
that image throught lzma -> 300 kB
compress idividual files -> 225 kB
It could make sense to include VSA and .. in
* Mitch Bradley <[EMAIL PROTECTED]> [061014 01:14]:
> c) The "tar-like minifilesystem" (the real name is "dropin format") is
> constructed by simple concatenation of individual "dropin modules".
Is this dropin format documented somewhere?
I am asking because I just invented the same thing a c
#72: LinuxBIOS needs to detect the DCON and communicate that information to the
kernel
--+-
Reporter: JordanCrouse |Owner: JordanCrouse
Type: enhancement | Status: closed
Priority: blocker
The tinderbox machine (pullcord) is offline pending some network
rearrangement. Should be back up in a few days.
--
Ivan Krstić <[EMAIL PROTECTED]> | GPG: 0x147C722D
___
Devel mailing list
Devel@laptop.org
http://mailman.laptop.org/mailman/listinfo/deve
24 matches
Mail list logo
