public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] DreamPlug - progress?
Date: Mon, 22 Aug 2011 18:04:44 +0200	[thread overview]
Message-ID: <201108221804.44301.marek.vasut@gmail.com> (raw)
In-Reply-To: <20110822152014.GC29321@titan.lakedaemon.net>

On Monday, August 22, 2011 05:20:14 PM Jason wrote:
> On Sat, Aug 20, 2011 at 11:53:41PM -0700, Prafulla Wadaskar wrote:
> > > -----Original Message-----
> > > From: u-boot-bounces at lists.denx.de
> > > [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Jason
> > > Sent: Sunday, August 21, 2011 6:09 AM
> > > To: Adam Baxter
> > > Cc: u-boot at lists.denx.de
> > > Subject: Re: [U-Boot] DreamPlug - progress?
> > > 
> > > On Sat, Aug 20, 2011 at 12:11:38PM +1000, Adam Baxter wrote:
> > > > Hi all,
> > > > I have a Globalscale Dreamplug
> > > > I wish to accomplish the following:
> > > > * Backup original uboot
> > > > * Verify original uboot
> > > > * Flash patched uboot to SPI
> > > > 
> > > > Any roadblocks? I couldn't confirm, either via this list or looking
> > > > at commits whether Dreamplug support ever made it back into mainline
> > > > uboot...
> > > 
> > > dreamplug patches have not been accepted into mainline because the
> > > proper way to do it (which globalscale didn't do in the binary they
> > > provided) is with a new machine id.  This is already reserved [1].
> > > U-boot shouldn't use the new mach-id until it is in mainline Linux.
> > > Linux won't accept new ARM boards unless they are moving towards device
> > > tree.
> > 
> > Is this something new?
> 
> Past six months or so...
> 
> > You just need machine-id in mach-types.h to get in dreamplug patches
> > mainlined into u-boot.
> 
> Yes, but mach-types.h is copied from Linux.  Until it makes it into
> Linux, it won't trickle down to U-Boot.

And here comes Russell ... if I count 5 pts for "f-word" and 1 pts for every 
other naughty word, I'm at 17 pts only today after discussing the mach-types 
issue ;-)

Anyway, the fix for the gplugd (is it the samy thing?) is in mainline I think and 
scheduled for 3.1.

> 
> > I have added earlier machine id through
> > http://www.arm.linux.org.uk/developer/machines/?action=new
> 
> Correct, this is how I added MACH_DREAMPLUG (3550).
> 
> > Doesn't this work now?
> 
> it should, however, Linus' tree only has up to #3494 [1].  RMK's
> database shows it, though [2].  Maybe I just need to be more patient.
> ;-)
> 
> thx,
> 
> Jason.
> 
> [1]
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=a
> rch/arm/tools/mach-types;h=fff68d0d521b095f0594fbf79bda99df8c3f21e4;hb=HEAD
> [2] http://www.arm.linux.org.uk/developer/machines/download.php
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot

  reply	other threads:[~2011-08-22 16:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-20  2:11 [U-Boot] DreamPlug - progress? Adam Baxter
2011-08-21  0:38 ` Jason
2011-08-21  6:53   ` Prafulla Wadaskar
2011-08-22 15:20     ` Jason
2011-08-22 16:04       ` Marek Vasut [this message]
2011-08-22 21:34         ` Adam Baxter
2011-08-22 21:37           ` Marek Vasut
2011-08-21  6:57 ` Prafulla Wadaskar
2011-08-21  7:17   ` Adam Baxter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201108221804.44301.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox