From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerry Van Baren Date: Wed, 24 Oct 2007 19:05:01 -0400 Subject: [U-Boot-Users] [RFC libfdt update][PATCH 1/2] Removed some nonused fdt functions and moved fdt_find_and_setprop out of libfdt In-Reply-To: <29786391-C862-4908-8FF8-A271B3BA6358@kernel.crashing.org> References: <471F7103.8090205@grandegger.com> <471F7A43.9050201@ge.com> <29786391-C862-4908-8FF8-A271B3BA6358@kernel.crashing.org> Message-ID: <471FCF9D.70808@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Kumar Gala wrote: > On Oct 24, 2007, at 12:00 PM, Jerry Van Baren wrote: > >> Wolfgang Grandegger wrote: >>> Kumar Gala wrote: >>>> Removed: >>>> fdt_node_is_compatible >>>> fdt_find_node_by_type >>>> fdt_find_compatible_node >>>> >>>> To ease merge of newer libfdt as we aren't using them anywhere at >>>> this time. >>> I use them for development (new projects). When can we expect the >>> new libfdt to be available in U-Boot? >>> Wolfgang. >> Hi Kumar, Wolfgang, >> >> My current thought is that we need a place above libfdt where we >> can put our convenience (and difference-of-opinion ;-) utility >> routines. >> >> I'm thinking >> common/fdt_support.c >> would be the place for this. Then Wolfgang G can put his fdt_* >> kernel-parallel routines (above) in there as well as the utility >> routine that Grant created (find & set, I forgot the exact name). > > Agreed, I moved Grant's fdt_find_and_setprop into common/fdt_support.c > > Also, realize there are equivalent functions to > fdt_node_is_compatible, etc. in the new libfdt. > > - k Ahh, right, the brain was shorted, too much caffeine, too little caffeine, its hard to get it balanced. My re-reading reminded me - question for Wolfgang Denk - are Doxygen tags in the source code acceptable? Best regards, gvb