public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] libfdt release?
Date: Mon, 15 Oct 2007 14:51:45 -0400	[thread overview]
Message-ID: <4713B6C1.5020204@ge.com> (raw)
In-Reply-To: <477B32C9-EC0F-4DB7-A1A1-C5E3041C9CDE@freescale.com>

Kumar Gala wrote:
> Guys,
> 
> Can you tell me where we stand on changes/additions to libfdt vs u- 
> boot.  I'd really like to see an updated libfdt imported into u-boot  
> for the next window and am happy to work on the u-boot modifications  
> as long as I understand what exactly they are.
> 
> Having fdt_get_name() and fdt_get_path() will be really useful for  
> some fixup of device node code I've got and will allow us to drop the  
> hard coded/explicit PATHs to nodes from <config.h>.
> 
> I'd rather see us take a clean libfdt drop rather than pulling in  
> bits and pieces.
> 
> - k

Hi Kumar,

My plan for the next merge window is to pull a fresh copy of The 
Official LIBFDT into u-boot-fdt.  From what David has said, libfdt has 
been filled out with some functions that we independently invented 
and/or there are better ways of doing things, if only we were smarter.

I have not had time to actually pull a copy of the current libfdt from 
the kernel/dtc repository and evaluate where we stand.

I would also like to see improvements to the 83xx CPU handling to match 
what Grant did on the 5xxx sub-repo.

My problem is that I had zero "u-boot" time available last month.  I 
have hopes for some time this month, but it is questionable.  Maybe 
November...

I don't anticipate a problem unforking libfdt, but it all takes time. 
Whatever you can contribute towards this, I'm happy to queue up for the 
next merge window.  If you have the time and desire to take over 
custodian responsibilities for u-boot-fdt, we can discuss that too.

Best regards,
gvb

  reply	other threads:[~2007-10-15 18:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <006E3CAD-11CB-4892-8BDB-9866677F371D@freescale.com>
     [not found] ` <20071010061458.GA6135@localhost.localdomain>
     [not found]   ` <912BB32E-FD7D-4CBC-AE3D-3D358E97DECB@freescale.com>
     [not found]     ` <20071011041239.GF14873@localhost.localdomain>
     [not found]       ` <9917D225-2082-4900-BFD4-96490EA88C42@freescale.com>
2007-10-11 23:35         ` [U-Boot-Users] libfdt release? Jerry Van Baren
2007-10-11 23:56           ` Detlev Zundel
2007-10-12  4:28           ` David Gibson
2007-10-12  7:16             ` Wolfgang Grandegger
2007-10-15  3:20               ` David Gibson
2007-10-12 11:58             ` Jerry Van Baren
2007-10-15  4:12               ` David Gibson
2007-10-15 18:30                 ` Kumar Gala
2007-10-15 18:51                   ` Jerry Van Baren [this message]
2007-10-15 19:03                     ` Kumar Gala
2007-10-15 19:23                       ` Jerry Van Baren
2007-10-15 21:50                         ` Kumar Gala
2007-10-15 19:21                   ` Wolfgang Grandegger
2007-10-16  2:44                     ` David Gibson
2007-10-16  7:03                       ` Wolfgang Grandegger
2007-10-16  7:19                         ` David Gibson
2007-10-23 14:39                 ` Kumar Gala
2007-10-23 23:51                   ` David Gibson

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=4713B6C1.5020204@ge.com \
    --to=gerald.vanbaren@ge.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