Bug 201291 - build olpc-kernel package for olpc hardware
Summary: build olpc-kernel package for olpc hardware
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Woodhouse
QA Contact: Brian Brock
URL:
Whiteboard:
: 201290 (view as bug list)
Depends On:
Blocks: OLPCTracker
TreeView+ depends on / blocked
 
Reported: 2006-08-04 03:01 UTC by Christopher Blizzard
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-01 17:25:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Christopher Blizzard 2006-08-04 03:01:41 UTC
Need to build out our olpc-kernel package for the hardware.  David Woodhouse has
a config file for the hardware here:

http://david.woodhou.se/olpc-config

That's apparently the _difference_ between the i686 config and OLPC.  There's
apparently a script in the kernel CVS that will build the config.

Comment 1 Dave Jones 2006-08-08 18:40:36 UTC
*** Bug 201290 has been marked as a duplicate of this bug. ***

Comment 2 Dave Jones 2006-08-08 18:48:33 UTC
Needs to be a set of overrides for the configs/ dir rather than a standalone
config file.

There's a number of oddities in the diff between 686 & OLPC that should fall out
if it's done this way, so I've not done a complete review of the changes.


Comment 3 Christopher Blizzard 2006-08-08 19:08:41 UTC
dwmw2 told me that that is what that file does - override the basic i686 config.
 Not sure if you were expecting a different format or something.

Comment 4 David Woodhouse 2006-08-09 08:47:45 UTC
No, I think I said (or certainly I _meant_ to say) that the scripts in the
kernel CVS directory are useful for making such 'config overrides' and that we
should so do instead of just using the raw file above.

Comment 5 Christopher Blizzard 2006-09-01 17:25:03 UTC
This is done, Marcelo has owned it.


Note You need to log in before you can comment on or make changes to this bug.