public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Enabling nand createbbt command
Date: Thu, 8 Mar 2012 17:03:57 -0600	[thread overview]
Message-ID: <4F593ADD.7090609@freescale.com> (raw)
In-Reply-To: <FD2DBC0E1365154BB0E3E348680BA0E902A1BF2A@nzc-ap-xch-03.ap.trimblecorp.net>

On 03/08/2012 04:49 PM, Bud Miljkovic wrote:
> 
> 
>> -----Original Message-----
>> From: Fabio Estevam [mailto:festevam at gmail.com]
>> Sent: Friday, 9 March 2012 11:45 a.m.
>> To: Bud Miljkovic
>> Cc: Scott Wood; u-boot at lists.denx.de
>> Subject: Re: [U-Boot] Enabling nand createbbt command
>>
>>
>> My suggestion is that you use U-boot from git.denx.de instead of the
>> 2009.08 from FSL.
> 
> Is that because the mainline U-boot id better maintained and/or ... ?

Well for once thing, it's because you're asking for help on the mailing
list for mainline U-Boot. :-)

We can't help you with some other codebase that we know nothing about.

I do expect mainline is better maintained and supported, except for
missing particular features/hardware support that nobody ever bothered
to submit to mainline -- which in this case appears to be hardware that
you care about, so unless you're prepared to do a fair bit of work to
add support to mainline, I'd try again to find a support channel for
your Freescale-provided U-Boot.  Or maybe we could help you figure out
what it is you want to do, instead of scrubbing, if the answer doesn't
depend on details of a non-standard U-Boot.

Oh, and if you're curious about my freescale.com e-mail address, I work
in a different part of the company and don't have i.MX knowledge or
contacts.

-Scott

  parent reply	other threads:[~2012-03-08 23:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08  1:56 [U-Boot] Enabling nand createbbt command Bud Miljkovic
2012-03-08 16:54 ` Scott Wood
2012-03-08 19:38   ` Bud Miljkovic
2012-03-08 20:02     ` Scott Wood
     [not found]       ` <FD2DBC0E1365154BB0E3E348680BA0E902A1BF24@nzc-ap-xch-03.ap.trimblecorp.net>
2012-03-08 21:08         ` Scott Wood
2012-03-08 21:22           ` Bud Miljkovic
2012-03-08 21:41             ` Fabio Estevam
     [not found]               ` <FD2DBC0E1365154BB0E3E348680BA0E902A1BF27@nzc-ap-xch-03.ap.trimblecorp.net>
2012-03-08 22:44                 ` Fabio Estevam
     [not found]                   ` <FD2DBC0E1365154BB0E3E348680BA0E902A1BF2A@nzc-ap-xch-03.ap.trimblecorp.net>
2012-03-08 23:03                     ` Scott Wood [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-03-08 22:08 Bud Miljkovic
2012-03-08 23:01 Bud Miljkovic
2012-03-08 23:10 ` Fabio Estevam
2012-03-09  0:58 Bud Miljkovic
2012-03-11 19:19 ` Charles Manning
2012-03-14  4:00   ` Bud Miljkovic
2012-03-14 17:23     ` Charles Manning
2012-03-18 23:09       ` Bud Miljkovic
2012-03-19 21:56         ` Charles Manning

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=4F593ADD.7090609@freescale.com \
    --to=scottwood@freescale.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