Patchwork [RFC] mkcard: Add a script to parition and format an SD Card

login
register
mail settings
Submitter Joel A Fernandes
Date Aug. 29, 2011, 6:12 a.m.
Message ID <1314598341-2793-1-git-send-email-joelagnel@ti.com>
Download mbox | patch
Permalink /patch/10705/
State New, archived
Headers show

Comments

Joel A Fernandes - Aug. 29, 2011, 6:12 a.m.
Script written by Graeme Gregory
http://www.angstrom-distribution.org/demo/beagleboard/mkcard.txt

Signed-off-by: Joel A Fernandes <joelagnel@ti.com>
Cc: Graeme Gregory <dp@xora.org.uk>
Cc: Jason Kridner <jdk@ti.com>
Cc: k-kooi@ti.com
---
 .../mkcard/mkcard-0.5/COPYING.patch                |  344 ++++++++++++++++++++
 meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt |   79 +++++
 meta/recipes-devtools/mkcard/mkcard_0.5.bb         |   19 +
 3 files changed, 442 insertions(+), 0 deletions(-)
 create mode 100644 meta/recipes-devtools/mkcard/mkcard-0.5/COPYING.patch
 create mode 100755 meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt
 create mode 100644 meta/recipes-devtools/mkcard/mkcard_0.5.bb
Joel A Fernandes - Aug. 29, 2011, 6:28 a.m.
On Mon, Aug 29, 2011 at 1:12 AM, Joel A Fernandes <joelagnel@ti.com> wrote:
> Script written by Graeme Gregory
> http://www.angstrom-distribution.org/demo/beagleboard/mkcard.txt
>
> Signed-off-by: Joel A Fernandes <joelagnel@ti.com>
> Cc: Graeme Gregory <dp@xora.org.uk>
> Cc: Jason Kridner <jdk@ti.com>
> Cc: k-kooi@ti.com
> ---

This script is to be run as native and will be used for SD Card image creation

>  .../mkcard/mkcard-0.5/COPYING.patch                |  344 ++++++++++++++++++++
>  meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt |   79 +++++
>  meta/recipes-devtools/mkcard/mkcard_0.5.bb         |   19 +
>  3 files changed, 442 insertions(+), 0 deletions(-)
>  create mode 100644 meta/recipes-devtools/mkcard/mkcard-0.5/COPYING.patch
>  create mode 100755 meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt
>  create mode 100644 meta/recipes-devtools/mkcard/mkcard_0.5.bb
>
> diff --git a/meta/recipes-devtools/mkcard/mkcard-0.5/COPYING.patch b/meta/recipes-devtools/mkcard/mkcard-0.5/COPYING.patch
> new file mode 100644
> index 0000000..c70eaf6
> --- /dev/null
> +++ b/meta/recipes-devtools/mkcard/mkcard-0.5/COPYING.patch
> @@ -0,0 +1,344 @@
> +diff -ruN mkcard-0.5-orig/COPYING mkdcard-0.5/COPYING
> +--- mkcard-0.5-orig/COPYING    1970-01-01 08:00:00.000000000 +0800
> ++++ mkcard-0.5/COPYING 2010-12-09 16:42:20.274984665 +0800
> +@@ -0,0 +1,340 @@
> ++                  GNU GENERAL PUBLIC LICENSE
> ++                     Version 2, June 1991
> ++
> ++ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
> ++                       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
> ++ Everyone is permitted to copy and distribute verbatim copies
> ++ of this license document, but changing it is not allowed.
> ++
> ++                          Preamble
> ++
> ++  The licenses for most software are designed to take away your
> ++freedom to share and change it.  By contrast, the GNU General Public
> ++License is intended to guarantee your freedom to share and change free
> ++software--to make sure the software is free for all its users.  This
> ++General Public License applies to most of the Free Software
> ++Foundation's software and to any other program whose authors commit to
> ++using it.  (Some other Free Software Foundation software is covered by
> ++the GNU Library General Public License instead.)  You can apply it to
> ++your programs, too.
> ++
> ++  When we speak of free software, we are referring to freedom, not
> ++price.  Our General Public Licenses are designed to make sure that you
> ++have the freedom to distribute copies of free software (and charge for
> ++this service if you wish), that you receive source code or can get it
> ++if you want it, that you can change the software or use pieces of it
> ++in new free programs; and that you know you can do these things.
> ++
> ++  To protect your rights, we need to make restrictions that forbid
> ++anyone to deny you these rights or to ask you to surrender the rights.
> ++These restrictions translate to certain responsibilities for you if you
> ++distribute copies of the software, or if you modify it.
> ++
> ++  For example, if you distribute copies of such a program, whether
> ++gratis or for a fee, you must give the recipients all the rights that
> ++you have.  You must make sure that they, too, receive or can get the
> ++source code.  And you must show them these terms so they know their
> ++rights.
> ++
> ++  We protect your rights with two steps: (1) copyright the software, and
> ++(2) offer you this license which gives you legal permission to copy,
> ++distribute and/or modify the software.
> ++
> ++  Also, for each author's protection and ours, we want to make certain
> ++that everyone understands that there is no warranty for this free
> ++software.  If the software is modified by someone else and passed on, we
> ++want its recipients to know that what they have is not the original, so
> ++that any problems introduced by others will not reflect on the original
> ++authors' reputations.
> ++
> ++  Finally, any free program is threatened constantly by software
> ++patents.  We wish to avoid the danger that redistributors of a free
> ++program will individually obtain patent licenses, in effect making the
> ++program proprietary.  To prevent this, we have made it clear that any
> ++patent must be licensed for everyone's free use or not licensed at all.
> ++
> ++  The precise terms and conditions for copying, distribution and
> ++modification follow.
> ++
> ++                  GNU GENERAL PUBLIC LICENSE
> ++   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
> ++
> ++  0. This License applies to any program or other work which contains
> ++a notice placed by the copyright holder saying it may be distributed
> ++under the terms of this General Public License.  The "Program", below,
> ++refers to any such program or work, and a "work based on the Program"
> ++means either the Program or any derivative work under copyright law:
> ++that is to say, a work containing the Program or a portion of it,
> ++either verbatim or with modifications and/or translated into another
> ++language.  (Hereinafter, translation is included without limitation in
> ++the term "modification".)  Each licensee is addressed as "you".
> ++
> ++Activities other than copying, distribution and modification are not
> ++covered by this License; they are outside its scope.  The act of
> ++running the Program is not restricted, and the output from the Program
> ++is covered only if its contents constitute a work based on the
> ++Program (independent of having been made by running the Program).
> ++Whether that is true depends on what the Program does.
> ++
> ++  1. You may copy and distribute verbatim copies of the Program's
> ++source code as you receive it, in any medium, provided that you
> ++conspicuously and appropriately publish on each copy an appropriate
> ++copyright notice and disclaimer of warranty; keep intact all the
> ++notices that refer to this License and to the absence of any warranty;
> ++and give any other recipients of the Program a copy of this License
> ++along with the Program.
> ++
> ++You may charge a fee for the physical act of transferring a copy, and
> ++you may at your option offer warranty protection in exchange for a fee.
> ++
> ++  2. You may modify your copy or copies of the Program or any portion
> ++of it, thus forming a work based on the Program, and copy and
> ++distribute such modifications or work under the terms of Section 1
> ++above, provided that you also meet all of these conditions:
> ++
> ++    a) You must cause the modified files to carry prominent notices
> ++    stating that you changed the files and the date of any change.
> ++
> ++    b) You must cause any work that you distribute or publish, that in
> ++    whole or in part contains or is derived from the Program or any
> ++    part thereof, to be licensed as a whole at no charge to all third
> ++    parties under the terms of this License.
> ++
> ++    c) If the modified program normally reads commands interactively
> ++    when run, you must cause it, when started running for such
> ++    interactive use in the most ordinary way, to print or display an
> ++    announcement including an appropriate copyright notice and a
> ++    notice that there is no warranty (or else, saying that you provide
> ++    a warranty) and that users may redistribute the program under
> ++    these conditions, and telling the user how to view a copy of this
> ++    License.  (Exception: if the Program itself is interactive but
> ++    does not normally print such an announcement, your work based on
> ++    the Program is not required to print an announcement.)
> ++
> ++These requirements apply to the modified work as a whole.  If
> ++identifiable sections of that work are not derived from the Program,
> ++and can be reasonably considered independent and separate works in
> ++themselves, then this License, and its terms, do not apply to those
> ++sections when you distribute them as separate works.  But when you
> ++distribute the same sections as part of a whole which is a work based
> ++on the Program, the distribution of the whole must be on the terms of
> ++this License, whose permissions for other licensees extend to the
> ++entire whole, and thus to each and every part regardless of who wrote it.
> ++
> ++Thus, it is not the intent of this section to claim rights or contest
> ++your rights to work written entirely by you; rather, the intent is to
> ++exercise the right to control the distribution of derivative or
> ++collective works based on the Program.
> ++
> ++In addition, mere aggregation of another work not based on the Program
> ++with the Program (or with a work based on the Program) on a volume of
> ++a storage or distribution medium does not bring the other work under
> ++the scope of this License.
> ++
> ++  3. You may copy and distribute the Program (or a work based on it,
> ++under Section 2) in object code or executable form under the terms of
> ++Sections 1 and 2 above provided that you also do one of the following:
> ++
> ++    a) Accompany it with the complete corresponding machine-readable
> ++    source code, which must be distributed under the terms of Sections
> ++    1 and 2 above on a medium customarily used for software interchange; or,
> ++
> ++    b) Accompany it with a written offer, valid for at least three
> ++    years, to give any third party, for a charge no more than your
> ++    cost of physically performing source distribution, a complete
> ++    machine-readable copy of the corresponding source code, to be
> ++    distributed under the terms of Sections 1 and 2 above on a medium
> ++    customarily used for software interchange; or,
> ++
> ++    c) Accompany it with the information you received as to the offer
> ++    to distribute corresponding source code.  (This alternative is
> ++    allowed only for noncommercial distribution and only if you
> ++    received the program in object code or executable form with such
> ++    an offer, in accord with Subsection b above.)
> ++
> ++The source code for a work means the preferred form of the work for
> ++making modifications to it.  For an executable work, complete source
> ++code means all the source code for all modules it contains, plus any
> ++associated interface definition files, plus the scripts used to
> ++control compilation and installation of the executable.  However, as a
> ++special exception, the source code distributed need not include
> ++anything that is normally distributed (in either source or binary
> ++form) with the major components (compiler, kernel, and so on) of the
> ++operating system on which the executable runs, unless that component
> ++itself accompanies the executable.
> ++
> ++If distribution of executable or object code is made by offering
> ++access to copy from a designated place, then offering equivalent
> ++access to copy the source code from the same place counts as
> ++distribution of the source code, even though third parties are not
> ++compelled to copy the source along with the object code.
> ++
> ++  4. You may not copy, modify, sublicense, or distribute the Program
> ++except as expressly provided under this License.  Any attempt
> ++otherwise to copy, modify, sublicense or distribute the Program is
> ++void, and will automatically terminate your rights under this License.
> ++However, parties who have received copies, or rights, from you under
> ++this License will not have their licenses terminated so long as such
> ++parties remain in full compliance.
> ++
> ++  5. You are not required to accept this License, since you have not
> ++signed it.  However, nothing else grants you permission to modify or
> ++distribute the Program or its derivative works.  These actions are
> ++prohibited by law if you do not accept this License.  Therefore, by
> ++modifying or distributing the Program (or any work based on the
> ++Program), you indicate your acceptance of this License to do so, and
> ++all its terms and conditions for copying, distributing or modifying
> ++the Program or works based on it.
> ++
> ++  6. Each time you redistribute the Program (or any work based on the
> ++Program), the recipient automatically receives a license from the
> ++original licensor to copy, distribute or modify the Program subject to
> ++these terms and conditions.  You may not impose any further
> ++restrictions on the recipients' exercise of the rights granted herein.
> ++You are not responsible for enforcing compliance by third parties to
> ++this License.
> ++
> ++  7. If, as a consequence of a court judgment or allegation of patent
> ++infringement or for any other reason (not limited to patent issues),
> ++conditions are imposed on you (whether by court order, agreement or
> ++otherwise) that contradict the conditions of this License, they do not
> ++excuse you from the conditions of this License.  If you cannot
> ++distribute so as to satisfy simultaneously your obligations under this
> ++License and any other pertinent obligations, then as a consequence you
> ++may not distribute the Program at all.  For example, if a patent
> ++license would not permit royalty-free redistribution of the Program by
> ++all those who receive copies directly or indirectly through you, then
> ++the only way you could satisfy both it and this License would be to
> ++refrain entirely from distribution of the Program.
> ++
> ++If any portion of this section is held invalid or unenforceable under
> ++any particular circumstance, the balance of the section is intended to
> ++apply and the section as a whole is intended to apply in other
> ++circumstances.
> ++
> ++It is not the purpose of this section to induce you to infringe any
> ++patents or other property right claims or to contest validity of any
> ++such claims; this section has the sole purpose of protecting the
> ++integrity of the free software distribution system, which is
> ++implemented by public license practices.  Many people have made
> ++generous contributions to the wide range of software distributed
> ++through that system in reliance on consistent application of that
> ++system; it is up to the author/donor to decide if he or she is willing
> ++to distribute software through any other system and a licensee cannot
> ++impose that choice.
> ++
> ++This section is intended to make thoroughly clear what is believed to
> ++be a consequence of the rest of this License.
> ++
> ++  8. If the distribution and/or use of the Program is restricted in
> ++certain countries either by patents or by copyrighted interfaces, the
> ++original copyright holder who places the Program under this License
> ++may add an explicit geographical distribution limitation excluding
> ++those countries, so that distribution is permitted only in or among
> ++countries not thus excluded.  In such case, this License incorporates
> ++the limitation as if written in the body of this License.
> ++
> ++  9. The Free Software Foundation may publish revised and/or new versions
> ++of the General Public License from time to time.  Such new versions will
> ++be similar in spirit to the present version, but may differ in detail to
> ++address new problems or concerns.
> ++
> ++Each version is given a distinguishing version number.  If the Program
> ++specifies a version number of this License which applies to it and "any
> ++later version", you have the option of following the terms and conditions
> ++either of that version or of any later version published by the Free
> ++Software Foundation.  If the Program does not specify a version number of
> ++this License, you may choose any version ever published by the Free Software
> ++Foundation.
> ++
> ++  10. If you wish to incorporate parts of the Program into other free
> ++programs whose distribution conditions are different, write to the author
> ++to ask for permission.  For software which is copyrighted by the Free
> ++Software Foundation, write to the Free Software Foundation; we sometimes
> ++make exceptions for this.  Our decision will be guided by the two goals
> ++of preserving the free status of all derivatives of our free software and
> ++of promoting the sharing and reuse of software generally.
> ++
> ++                          NO WARRANTY
> ++
> ++  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
> ++FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
> ++OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
> ++PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
> ++OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
> ++MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
> ++TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
> ++PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
> ++REPAIR OR CORRECTION.
> ++
> ++  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
> ++WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
> ++REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
> ++INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
> ++OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
> ++TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
> ++YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
> ++PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
> ++POSSIBILITY OF SUCH DAMAGES.
> ++
> ++                   END OF TERMS AND CONDITIONS
> ++
> ++          How to Apply These Terms to Your New Programs
> ++
> ++  If you develop a new program, and you want it to be of the greatest
> ++possible use to the public, the best way to achieve this is to make it
> ++free software which everyone can redistribute and change under these terms.
> ++
> ++  To do so, attach the following notices to the program.  It is safest
> ++to attach them to the start of each source file to most effectively
> ++convey the exclusion of warranty; and each file should have at least
> ++the "copyright" line and a pointer to where the full notice is found.
> ++
> ++    <one line to give the program's name and a brief idea of what it does.>
> ++    Copyright (C) <year>  <name of author>
> ++
> ++    This program is free software; you can redistribute it and/or modify
> ++    it under the terms of the GNU General Public License as published by
> ++    the Free Software Foundation; either version 2 of the License, or
> ++    (at your option) any later version.
> ++
> ++    This program is distributed in the hope that it will be useful,
> ++    but WITHOUT ANY WARRANTY; without even the implied warranty of
> ++    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> ++    GNU General Public License for more details.
> ++
> ++    You should have received a copy of the GNU General Public License
> ++    along with this program; if not, write to the Free Software
> ++    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
> ++
> ++
> ++Also add information on how to contact you by electronic and paper mail.
> ++
> ++If the program is interactive, make it output a short notice like this
> ++when it starts in an interactive mode:
> ++
> ++    Gnomovision version 69, Copyright (C) year name of author
> ++    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
> ++    This is free software, and you are welcome to redistribute it
> ++    under certain conditions; type `show c' for details.
> ++
> ++The hypothetical commands `show w' and `show c' should show the appropriate
> ++parts of the General Public License.  Of course, the commands you use may
> ++be called something other than `show w' and `show c'; they could even be
> ++mouse-clicks or menu items--whatever suits your program.
> ++
> ++You should also get your employer (if you work as a programmer) or your
> ++school, if any, to sign a "copyright disclaimer" for the program, if
> ++necessary.  Here is a sample; alter the names:
> ++
> ++  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
> ++  `Gnomovision' (which makes passes at compilers) written by James Hacker.
> ++
> ++  <signature of Ty Coon>, 1 April 1989
> ++  Ty Coon, President of Vice
> ++
> ++This General Public License does not permit incorporating your program into
> ++proprietary programs.  If your program is a subroutine library, you may
> ++consider it more useful to permit linking proprietary applications with the
> ++library.  If this is what you want to do, use the GNU Library General
> ++Public License instead of this License.
> diff --git a/meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt b/meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt
> new file mode 100755
> index 0000000..743b36d
> --- /dev/null
> +++ b/meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt
> @@ -0,0 +1,79 @@
> +#! /bin/sh
> +# mkcard.sh v0.5
> +# (c) Copyright 2009 Graeme Gregory <dp@xora.org.uk>
> +# Licensed under terms of GPLv2
> +#
> +# Parts of the procudure base on the work of Denys Dmytriyenko
> +# http://wiki.omap.com/index.php/MMC_Boot_Format
> +
> +export LC_ALL=C
> +
> +if [ $# -ne 1 ]; then
> +       echo "Usage: $0 <drive>"
> +       exit 1;
> +fi
> +
> +DRIVE=$1
> +
> +dd if=/dev/zero of=$DRIVE bs=1024 count=1024
> +
> +SIZE=`fdisk -l $DRIVE | grep Disk | grep bytes | awk '{print $5}'`
> +
> +echo DISK SIZE - $SIZE bytes
> +
> +CYLINDERS=`echo $SIZE/255/63/512 | bc`
> +
> +echo CYLINDERS - $CYLINDERS
> +
> +{
> +echo ,9,0x0C,*
> +echo ,,,-
> +} | sfdisk -D -H 255 -S 63 -C $CYLINDERS $DRIVE
> +
> +sleep 1
> +
> +
> +if [ -x `which kpartx` ]; then
> +       kpartx -a ${DRIVE}
> +fi
> +
> +# handle various device names.
> +# note something like fdisk -l /dev/loop0 | egrep -E '^/dev' | cut -d' ' -f1
> +# won't work due to https://bugzilla.redhat.com/show_bug.cgi?id=649572
> +
> +PARTITION1=${DRIVE}1
> +if [ ! -b ${PARTITION1} ]; then
> +       PARTITION1=${DRIVE}p1
> +fi
> +
> +DRIVE_NAME=`basename $DRIVE`
> +DEV_DIR=`dirname $DRIVE`
> +
> +if [ ! -b ${PARTITION1} ]; then
> +       PARTITION1=$DEV_DIR/mapper/${DRIVE_NAME}p1
> +fi
> +
> +PARTITION2=${DRIVE}2
> +if [ ! -b ${PARTITION2} ]; then
> +       PARTITION2=${DRIVE}p2
> +fi
> +if [ ! -b ${PARTITION2} ]; then
> +       PARTITION2=$DEV_DIR/mapper/${DRIVE_NAME}p2
> +fi
> +
> +
> +# now make partitions.
> +if [ -b ${PARTITION1} ]; then
> +       umount ${PARTITION1}
> +       mkfs.vfat -F 32 -n "boot" ${PARTITION1}
> +else
> +       echo "Cant find boot partition in /dev"
> +fi
> +
> +if [ -b ${PARITION2} ]; then
> +       umount ${PARTITION2}
> +       mke2fs -j -L "Angstrom" ${PARTITION2}
> +else
> +       echo "Cant find rootfs partition in /dev"
> +fi
> +
> diff --git a/meta/recipes-devtools/mkcard/mkcard_0.5.bb b/meta/recipes-devtools/mkcard/mkcard_0.5.bb
> new file mode 100644
> index 0000000..4d4a642
> --- /dev/null
> +++ b/meta/recipes-devtools/mkcard/mkcard_0.5.bb
> @@ -0,0 +1,19 @@
> +inherit native
> +
> +DESCRIPTION = "A tool to format SD Cards correctly"
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
> +SECTION = "base"
> +SRC_URI = "file://mkcard.txt \
> +           file://COPYING.patch"
> +PR = "r0"
> +
> +do_configure() {
> +        install -m 0755 ${WORKDIR}/mkcard.txt ${S}/
> +}
> +
> +do_install() {
> +       install -d ${D}${base_sbindir}
> +       install -m 0755 ${S}/mkcard.txt ${D}${base_sbindir}/mkcard
> +}
> +
> --
> 1.7.0.4
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Koen Kooi - Aug. 29, 2011, 7:58 a.m.
Op 29 aug. 2011, om 08:12 heeft Joel A Fernandes het volgende geschreven:

> Script written by Graeme Gregory
> http://www.angstrom-distribution.org/demo/beagleboard/mkcard.txt
> 
> Signed-off-by: Joel A Fernandes <joelagnel@ti.com>
> Cc: Graeme Gregory <dp@xora.org.uk>
> Cc: Jason Kridner <jdk@ti.com>
> Cc: k-kooi@ti.com
> ---
> .../mkcard/mkcard-0.5/COPYING.patch                |  344 ++++++++++++++++++++
> meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt |   79 +++++
> meta/recipes-devtools/mkcard/mkcard_0.5.bb         |   19 +
> 3 files changed, 442 insertions(+), 0 deletions(-)
> create mode 100644 meta/recipes-devtools/mkcard/mkcard-0.5/COPYING.patch
> create mode 100755 meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt
> create mode 100644 meta/recipes-devtools/mkcard/mkcard_0.5.bb

This script is BSP specific and shouldn't live in the OE-core layer.
Andrea Adami - Aug. 29, 2011, 1:32 p.m.
I was exactly wondering about the necessity of such
script...formatting an SD is not rocket science.
If it is handy for  beagleboard then put it in its BSP.
Andrea

2011/8/29, Koen Kooi <koen@dominion.thruhere.net>:
>
> Op 29 aug. 2011, om 08:12 heeft Joel A Fernandes het volgende geschreven:
>
>> Script written by Graeme Gregory
>> http://www.angstrom-distribution.org/demo/beagleboard/mkcard.txt
>>
>> Signed-off-by: Joel A Fernandes <joelagnel@ti.com>
>> Cc: Graeme Gregory <dp@xora.org.uk>
>> Cc: Jason Kridner <jdk@ti.com>
>> Cc: k-kooi@ti.com
>> ---
>> .../mkcard/mkcard-0.5/COPYING.patch                |  344
>> ++++++++++++++++++++
>> meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt |   79 +++++
>> meta/recipes-devtools/mkcard/mkcard_0.5.bb         |   19 +
>> 3 files changed, 442 insertions(+), 0 deletions(-)
>> create mode 100644 meta/recipes-devtools/mkcard/mkcard-0.5/COPYING.patch
>> create mode 100755 meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt
>> create mode 100644 meta/recipes-devtools/mkcard/mkcard_0.5.bb
>
> This script is BSP specific and shouldn't live in the OE-core layer.
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Joel A Fernandes - Aug. 29, 2011, 1:37 p.m.
On Mon, Aug 29, 2011 at 8:32 AM, Andrea Adami <andrea.adami@gmail.com> wrote:
> I was exactly wondering about the necessity of such
> script...formatting an SD is not rocket science.
> If it is handy for  beagleboard then put it in its BSP.

So everything in oe-core is rocket science? ;) Just kidding

sure I'll move it over to meta-texasinstruments

thanks,
Joel
Joel A Fernandes - Aug. 29, 2011, 3:10 p.m.
On Mon, Aug 29, 2011 at 2:58 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>
> Op 29 aug. 2011, om 08:12 heeft Joel A Fernandes het volgende geschreven:
>
>> Script written by Graeme Gregory
>> http://www.angstrom-distribution.org/demo/beagleboard/mkcard.txt
>>
>> Signed-off-by: Joel A Fernandes <joelagnel@ti.com>
>> Cc: Graeme Gregory <dp@xora.org.uk>
>> Cc: Jason Kridner <jdk@ti.com>
>> Cc: k-kooi@ti.com
>> ---
>> .../mkcard/mkcard-0.5/COPYING.patch                |  344 ++++++++++++++++++++
>> meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt |   79 +++++
>> meta/recipes-devtools/mkcard/mkcard_0.5.bb         |   19 +
>> 3 files changed, 442 insertions(+), 0 deletions(-)
>> create mode 100644 meta/recipes-devtools/mkcard/mkcard-0.5/COPYING.patch
>> create mode 100755 meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt
>> create mode 100644 meta/recipes-devtools/mkcard/mkcard_0.5.bb
>
> This script is BSP specific and shouldn't live in the OE-core layer.

The only issue is this script is used from within the IMAGE_CMD_sdimg
code which lives in OE-core (meta/classes/image_types.bbclass)

thanks
Joel
Koen Kooi - Aug. 29, 2011, 5:33 p.m.
Op 29 aug. 2011 om 17:10 heeft Joel A Fernandes <agnel.joel@gmail.com> het volgende geschreven:

> On Mon, Aug 29, 2011 at 2:58 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>> 
>> Op 29 aug. 2011, om 08:12 heeft Joel A Fernandes het volgende geschreven:
>> 
>>> Script written by Graeme Gregory
>>> http://www.angstrom-distribution.org/demo/beagleboard/mkcard.txt
>>> 
>>> Signed-off-by: Joel A Fernandes <joelagnel@ti.com>
>>> Cc: Graeme Gregory <dp@xora.org.uk>
>>> Cc: Jason Kridner <jdk@ti.com>
>>> Cc: k-kooi@ti.com
>>> ---
>>> .../mkcard/mkcard-0.5/COPYING.patch                |  344 ++++++++++++++++++++
>>> meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt |   79 +++++
>>> meta/recipes-devtools/mkcard/mkcard_0.5.bb         |   19 +
>>> 3 files changed, 442 insertions(+), 0 deletions(-)
>>> create mode 100644 meta/recipes-devtools/mkcard/mkcard-0.5/COPYING.patch
>>> create mode 100755 meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt
>>> create mode 100644 meta/recipes-devtools/mkcard/mkcard_0.5.bb
>> 
>> This script is BSP specific and shouldn't live in the OE-core layer.
> 
> The only issue is this script is used from within the IMAGE_CMD_sdimg
> code which lives in OE-core (meta/classes/image_types.

classes shouldn't be calling external scripts


> 
> thanks
> Joel
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Jason Kridner - Aug. 29, 2011, 9:03 p.m.
>>>
>>> This script is BSP specific and shouldn't live in the OE-core layer.
>>
>> The only issue is this script is used from within the IMAGE_CMD_sdimg
>> code which lives in OE-core (meta/classes/image_types.
>
> classes shouldn't be calling external scripts
>

Is the right approach to add parameters to the IMAGE_CMD_sdimg class
such that it can be used generically to produce SD card images,
instead of trying to move this to meta-ti?  Should it perhaps be a bit
closer to what is being done by the Linaro image tools [1]?

[1] https://wiki.linaro.org/Source/ImageBuilding
Joel A Fernandes - Aug. 29, 2011, 11:08 p.m.
On Mon, Aug 29, 2011 at 4:03 PM, Jason Kridner <jkridner@beagleboard.org> wrote:
>>>>
>>>> This script is BSP specific and shouldn't live in the OE-core layer.
>>>
>>> The only issue is this script is used from within the IMAGE_CMD_sdimg
>>> code which lives in OE-core (meta/classes/image_types.
>>
>> classes shouldn't be calling external scripts
>>
>
> Is the right approach to add parameters to the IMAGE_CMD_sdimg class
> such that it can be used generically to produce SD card images,
> instead of trying to move this to meta-ti?  Should it perhaps be a bit
> closer to what is being done by the Linaro image tools [1]?
>
> [1] https://wiki.linaro.org/Source/ImageBuilding
>

Don't the Linaro scripts need to run on the target? Does it fit well
with OE(-core) ?

I took lot of pain to write it for OE and its almost done, so suggest
we use my method atleast for a few days ;-)

Thanks
Joel
Koen Kooi - Aug. 30, 2011, 7:13 a.m.
Op 30 aug. 2011, om 01:08 heeft Joel A Fernandes het volgende geschreven:

> On Mon, Aug 29, 2011 at 4:03 PM, Jason Kridner <jkridner@beagleboard.org> wrote:
>>>>> 
>>>>> This script is BSP specific and shouldn't live in the OE-core layer.
>>>> 
>>>> The only issue is this script is used from within the IMAGE_CMD_sdimg
>>>> code which lives in OE-core (meta/classes/image_types.
>>> 
>>> classes shouldn't be calling external scripts
>>> 
>> 
>> Is the right approach to add parameters to the IMAGE_CMD_sdimg class
>> such that it can be used generically to produce SD card images,
>> instead of trying to move this to meta-ti?  Should it perhaps be a bit
>> closer to what is being done by the Linaro image tools [1]?
>> 
>> [1] https://wiki.linaro.org/Source/ImageBuilding
>> 
> 
> Don't the Linaro scripts need to run on the target? Does it fit well
> with OE(-core) ?
> 
> I took lot of pain to write it for OE and its almost done, so suggest
> we use my method atleast for a few days ;-)

I'm immune to the "but I spent a lot of time on this" type of arguments
Richard Purdie - Aug. 30, 2011, 9:31 a.m.
On Mon, 2011-08-29 at 17:03 -0400, Jason Kridner wrote:
> >>>
> >>> This script is BSP specific and shouldn't live in the OE-core layer.
> >>
> >> The only issue is this script is used from within the IMAGE_CMD_sdimg
> >> code which lives in OE-core (meta/classes/image_types.
> >
> > classes shouldn't be calling external scripts
> >
> 
> Is the right approach to add parameters to the IMAGE_CMD_sdimg class
> such that it can be used generically to produce SD card images,
> instead of trying to move this to meta-ti?  Should it perhaps be a bit
> closer to what is being done by the Linaro image tools [1]?
> 
> [1] https://wiki.linaro.org/Source/ImageBuilding

I have heard multiple requests for making general SD card (or USB stick)
style images so I would love to see something generic. The script as it
stands looks like it has some issues due to requiring root access
(and/or special mounts).

There was a previous attempt at this in OE-Core:

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/classes/boot-directdisk.bbclass

but this has some issues making assumptions about sector size that
caused problems. On the  plus side it demonstrated it was possible
without root...

Cheers,

Richard
Graeme Gregory - Aug. 30, 2011, 9:36 a.m.
On 30/08/2011 10:31, Richard Purdie wrote:
> On Mon, 2011-08-29 at 17:03 -0400, Jason Kridner wrote:
>>>>> This script is BSP specific and shouldn't live in the OE-core layer.
>>>> The only issue is this script is used from within the IMAGE_CMD_sdimg
>>>> code which lives in OE-core (meta/classes/image_types.
>>> classes shouldn't be calling external scripts
>>>
>> Is the right approach to add parameters to the IMAGE_CMD_sdimg class
>> such that it can be used generically to produce SD card images,
>> instead of trying to move this to meta-ti?  Should it perhaps be a bit
>> closer to what is being done by the Linaro image tools [1]?
>>
>> [1] https://wiki.linaro.org/Source/ImageBuilding
> I have heard multiple requests for making general SD card (or USB stick)
> style images so I would love to see something generic. The script as it
> stands looks like it has some issues due to requiring root access
> (and/or special mounts).
>
As the author again, its totally unsuitable and was never designed for
doing that.

Graeme
Koen Kooi - Aug. 30, 2011, 10:34 a.m.
Op 30 aug. 2011, om 11:36 heeft Graeme Gregory het volgende geschreven:

> On 30/08/2011 10:31, Richard Purdie wrote:
>> On Mon, 2011-08-29 at 17:03 -0400, Jason Kridner wrote:
>>>>>> This script is BSP specific and shouldn't live in the OE-core layer.
>>>>> The only issue is this script is used from within the IMAGE_CMD_sdimg
>>>>> code which lives in OE-core (meta/classes/image_types.
>>>> classes shouldn't be calling external scripts
>>>> 
>>> Is the right approach to add parameters to the IMAGE_CMD_sdimg class
>>> such that it can be used generically to produce SD card images,
>>> instead of trying to move this to meta-ti?  Should it perhaps be a bit
>>> closer to what is being done by the Linaro image tools [1]?
>>> 
>>> [1] https://wiki.linaro.org/Source/ImageBuilding
>> I have heard multiple requests for making general SD card (or USB stick)
>> style images so I would love to see something generic. The script as it
>> stands looks like it has some issues due to requiring root access
>> (and/or special mounts).
>> 
> As the author again, its totally unsuitable and was never designed for
> doing that.

To clarify, it deals only with the slightly weird formatting needed by the OMAP3/4 boot ROM to get the bootloader from FAT and not with generic sd card images.

regards,

Koen
Graeme Gregory - Aug. 30, 2011, 10:38 a.m.
On 30/08/2011 11:34, Koen Kooi wrote:
> Op 30 aug. 2011, om 11:36 heeft Graeme Gregory het volgende geschreven:
>
>> On 30/08/2011 10:31, Richard Purdie wrote:
>>> On Mon, 2011-08-29 at 17:03 -0400, Jason Kridner wrote:
>>>>>>> This script is BSP specific and shouldn't live in the OE-core layer.
>>>>>> The only issue is this script is used from within the IMAGE_CMD_sdimg
>>>>>> code which lives in OE-core (meta/classes/image_types.
>>>>> classes shouldn't be calling external scripts
>>>>>
>>>> Is the right approach to add parameters to the IMAGE_CMD_sdimg class
>>>> such that it can be used generically to produce SD card images,
>>>> instead of trying to move this to meta-ti?  Should it perhaps be a bit
>>>> closer to what is being done by the Linaro image tools [1]?
>>>>
>>>> [1] https://wiki.linaro.org/Source/ImageBuilding
>>> I have heard multiple requests for making general SD card (or USB stick)
>>> style images so I would love to see something generic. The script as it
>>> stands looks like it has some issues due to requiring root access
>>> (and/or special mounts).
>>>
>> As the author again, its totally unsuitable and was never designed for
>> doing that.
> To clarify, it deals only with the slightly weird formatting needed by the OMAP3/4 boot ROM to get the bootloader from FAT and not with generic sd card images.
>
I actually meant the script is unsuitable for use within bitbake. The
format is actually very generic. An aweful lot of embedded systems
require MSDOS compatible partition tables which is basically what the
script creates. parted sucks as it doesnt have a simple way to say make
this msdos compatible.

Graeme
Jason Kridner - Aug. 30, 2011, 4:46 p.m.
On Mon, Aug 29, 2011 at 7:08 PM, Joel A Fernandes <agnel.joel@gmail.com> wrote:
> On Mon, Aug 29, 2011 at 4:03 PM, Jason Kridner <jkridner@beagleboard.org> wrote:
>>>>>
>>>>> This script is BSP specific and shouldn't live in the OE-core layer.
>>>>
>>>> The only issue is this script is used from within the IMAGE_CMD_sdimg
>>>> code which lives in OE-core (meta/classes/image_types.
>>>
>>> classes shouldn't be calling external scripts
>>>
>>
>> Is the right approach to add parameters to the IMAGE_CMD_sdimg class
>> such that it can be used generically to produce SD card images,
>> instead of trying to move this to meta-ti?  Should it perhaps be a bit
>> closer to what is being done by the Linaro image tools [1]?
>>
>> [1] https://wiki.linaro.org/Source/ImageBuilding
>>
>
> Don't the Linaro scripts need to run on the target?

No.

> Does it fit well
> with OE(-core) ?

I don't know, but I hoped that others would comment to help figure it
out.  I think it is a common challenge not just for ARM architectures.
 I'm not sure if the approach is general enough or not, but it does go
beyond the BeagleBoard.

My primary concerns about leaving it in the BSP are:
1) that there is some room for non-BeagleBoard specific optimizations
to the card layout and
2) there may be improvements to the tools that make it easier to
create images for systems with different boot requirements.

Also, I think we might want to move to an ext3 partition only in the
future or other such layout optimizations.  I'd like that to be
something that can be parameterized by the BSP.

>
> I took lot of pain to write it for OE and its almost done, so suggest
> we use my method atleast for a few days ;-)
>
> Thanks
> Joel
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Koen Kooi - Aug. 30, 2011, 5:47 p.m.
Op 30 aug. 2011, om 18:46 heeft Jason Kridner het volgende geschreven:

> On Mon, Aug 29, 2011 at 7:08 PM, Joel A Fernandes <agnel.joel@gmail.com> wrote:
>> On Mon, Aug 29, 2011 at 4:03 PM, Jason Kridner <jkridner@beagleboard.org> wrote:
>>>>>> 
>>>>>> This script is BSP specific and shouldn't live in the OE-core layer.
>>>>> 
>>>>> The only issue is this script is used from within the IMAGE_CMD_sdimg
>>>>> code which lives in OE-core (meta/classes/image_types.
>>>> 
>>>> classes shouldn't be calling external scripts
>>>> 
>>> 
>>> Is the right approach to add parameters to the IMAGE_CMD_sdimg class
>>> such that it can be used generically to produce SD card images,
>>> instead of trying to move this to meta-ti?  Should it perhaps be a bit
>>> closer to what is being done by the Linaro image tools [1]?
>>> 
>>> [1] https://wiki.linaro.org/Source/ImageBuilding
>>> 
>> 
>> Don't the Linaro scripts need to run on the target?
> 
> No.
> 
>> Does it fit well
>> with OE(-core) ?
> 
> I don't know, but I hoped that others would comment to help figure it
> out.  I think it is a common challenge not just for ARM architectures.
> I'm not sure if the approach is general enough or not, but it does go
> beyond the BeagleBoard.
> 
> My primary concerns about leaving it in the BSP are:
> 1) that there is some room for non-BeagleBoard specific optimizations
> to the card layout and
> 2) there may be improvements to the tools that make it easier to
> create images for systems with different boot requirements.
> 
> Also, I think we might want to move to an ext3 partition only in the
> future or other such layout optimizations.  I'd like that to be
> something that can be parameterized by the BSP.

I think you're missing the point:

The *script* needs to go into the BSP, you are free to extend the bbclasses with code to deal with sd cards internally in OE-core.


> 
>> 
>> I took lot of pain to write it for OE and its almost done, so suggest
>> we use my method atleast for a few days ;-)
>> 
>> Thanks
>> Joel
>> 
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Joel A Fernandes - Aug. 30, 2011, 9:08 p.m.
On Tue, Aug 30, 2011 at 12:47 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>
> Op 30 aug. 2011, om 18:46 heeft Jason Kridner het volgende geschreven:
>
>> On Mon, Aug 29, 2011 at 7:08 PM, Joel A Fernandes <agnel.joel@gmail.com> wrote:
>>> On Mon, Aug 29, 2011 at 4:03 PM, Jason Kridner <jkridner@beagleboard.org> wrote:
>>>>>>>
>>>>>>> This script is BSP specific and shouldn't live in the OE-core layer.
>>>>>>
>>>>>> The only issue is this script is used from within the IMAGE_CMD_sdimg
>>>>>> code which lives in OE-core (meta/classes/image_types.
>>>>>
>>>>> classes shouldn't be calling external scripts
>>>>>
>>>>
>>>> Is the right approach to add parameters to the IMAGE_CMD_sdimg class
>>>> such that it can be used generically to produce SD card images,
>>>> instead of trying to move this to meta-ti?  Should it perhaps be a bit
>>>> closer to what is being done by the Linaro image tools [1]?
>>>>
>>>> [1] https://wiki.linaro.org/Source/ImageBuilding
>>>>
>>>
>>> Don't the Linaro scripts need to run on the target?
>>
>> No.
>>
>>> Does it fit well
>>> with OE(-core) ?
>>
>> I don't know, but I hoped that others would comment to help figure it
>> out.  I think it is a common challenge not just for ARM architectures.
>> I'm not sure if the approach is general enough or not, but it does go
>> beyond the BeagleBoard.
>>
>> My primary concerns about leaving it in the BSP are:
>> 1) that there is some room for non-BeagleBoard specific optimizations
>> to the card layout and
>> 2) there may be improvements to the tools that make it easier to
>> create images for systems with different boot requirements.
>>
>> Also, I think we might want to move to an ext3 partition only in the
>> future or other such layout optimizations.  I'd like that to be
>> something that can be parameterized by the BSP.
>
> I think you're missing the point:
>
> The *script* needs to go into the BSP, you are free to extend the bbclasses with code to deal with sd cards internally in OE-core.
>
>

I think there are 2 threads to this discussion. One talks about mkcard
script (which I think Koen is asking to move to BSP), and the other is
the IMAGE_CMD_sdimg variable from image_types.bbclass which holds the
code to create the image (which Jason is referring to).

I am dropping mkcard script as it requires root access (due to kparted
and device mapper), instead I'm just using loop and avoiding device
mapper.

As for the IMAGE_CMD_sdimg , I'm thinking a clean way is to extend
image_types.bbclass from within the BSP layer (which I think Koen also
is suggesting).

Maybe I'm just summarizing what everyone is saying, but just making
sure everyone is on the same page.

Thanks,
Joel
Joel A Fernandes - Sept. 2, 2011, 3:44 p.m.
On Tue, Aug 30, 2011 at 12:47 PM, Koen Kooi <koen@dominion.thruhere.net>
wrote:
>
> Op 30 aug. 2011, om 18:46 heeft Jason Kridner het volgende geschreven:
>
>> On Mon, Aug 29, 2011 at 7:08 PM, Joel A Fernandes <agnel.joel@gmail.com>
wrote:
>>> On Mon, Aug 29, 2011 at 4:03 PM, Jason Kridner <jkridner@beagleboard.org>
wrote:
>>>>>>>
>>>>>>> This script is BSP specific and shouldn't live in the OE-core layer.
>>>>>>
>>>>>> The only issue is this script is used from within the IMAGE_CMD_sdimg
>>>>>> code which lives in OE-core (meta/classes/image_types.
>>>>>
>>>>> classes shouldn't be calling external scripts
>>>>>
>>>>
>>>> Is the right approach to add parameters to the IMAGE_CMD_sdimg class
>>>> such that it can be used generically to produce SD card images,
>>>> instead of trying to move this to meta-ti?  Should it perhaps be a bit
>>>> closer to what is being done by the Linaro image tools [1]?
>>>>
>>>> [1] https://wiki.linaro.org/Source/ImageBuilding
>>>>
>>>
>>> Don't the Linaro scripts need to run on the target?
>>
>> No.
>>
>>> Does it fit well
>>> with OE(-core) ?
>>
>> I don't know, but I hoped that others would comment to help figure it
>> out.  I think it is a common challenge not just for ARM architectures.
>> I'm not sure if the approach is general enough or not, but it does go
>> beyond the BeagleBoard.
>>
>> My primary concerns about leaving it in the BSP are:
>> 1) that there is some room for non-BeagleBoard specific optimizations
>> to the card layout and
>> 2) there may be improvements to the tools that make it easier to
>> create images for systems with different boot requirements.
>>
>> Also, I think we might want to move to an ext3 partition only in the
>> future or other such layout optimizations.  I'd like that to be
>> something that can be parameterized by the BSP.
>
> I think you're missing the point:
>
> The *script* needs to go into the BSP, you are free to extend the
bbclasses with code to deal with sd cards internally in OE-core.
>
>

Hi Koen,

Can you suggest how we proceed with extending the bbclass?

I have tried both .bbappend and BBCLASSEXTEND and didn't get it to work.

I could create a new class and inherit the oe-core one from it with tweaks.

Here is complete IRC discussion between me and bluelightning on the
reasoning to extend the image.bbclass:

* cminyard (~cminyard@pool-173-57-155-71.dllstx.fios.verizon.net) has joined
#oe
<joelagnel> I'd like to extend a bbclass in oe-core with tweaks in another
layer
<joelagnel> What is the right way to do so? .bbappend ? BBCLASSEXTEND?
<GNUtoo|work> JaMa|Wrk, btw I've also another patch:
<GNUtoo|work> at eukrea we use ubifs, and had the exact same issue than the
freerunner ubifs issue, at least it seems
<GNUtoo|work> we fixed it
<GNUtoo|work> so if the patch arrived, it should fix it for you too
<GNUtoo|work> joelagnel, BBCLASSEXTEND seem for recipes
<joelagnel> I've seen it for classes in meta-oe:
<joelagnel> ../meta-openembedded/meta-oe/classes/gnome.bbclass:BBCLASSEXTEND
+= "native"
<joelagnel> GNUtoo|work, but it doesn't do what I want
<joelagnel> I can create a new class, inherit from the oe-core one and put
my code there, but I think that'll get rejected ;)
<GNUtoo|work> ok
<GNUtoo|work> maybe ask in the list
<joelagnel> everyone here on long weekend holiday? ;)
* hollisb (~hollisb@c-24-20-193-174.hsd1.or.comcast.net) has joined #oe
<bluelightning> joelagnel: I don't think bbclassextend is what you want
<bluelightning> what tweaks do you want to apply?
<joelagnel> bluelightning, can I name a class in an upper layer with the
same filename as that of a lower layer, and still be able to inherit the
lower layer one?
<bluelightning> I don't think you can do it that way no
<bluelightning> if it's the same name it will just replace it effectively
<bluelightning> the most likely result in that case is you'll get a circular
reference
<joelagnel> BlindMan, there was some talk about moving my changes
(IMAGE_CMD_sdimg) to the bsp layer
<joelagnel>
https://github.com/joelagnel/oe-core/blob/db4c960da57e8e0ae4741eea703a4e163c589efa/meta/classes/image_types.bbclass
<joelagnel> sorry I meant bluelightning ;)
<joelagnel> need coffee!!! :-D
<joelagnel> and need .bbclassappend ;)
* msm (~msm@192.88.168.35) has joined #oe
<bluelightning> hmm; this is an interesting one
<bluelightning> I recall the discussion on the mailing list... I do wonder
whether we ought to try to find a way to get this into oe-core itself
* phdeswer has quit (Ping timeout: 276 seconds)
<joelagnel> bluelightning, I'm copying in a ubi file into the rootfs which I
don't think is generic enough
<joelagnel> also all sorts of assumptions are made about bootloader file
names (U-boot, uEnv, user.txt) etc
<bluelightning> hmm
<bluelightning> is this only likely to be applicable to one machine then?
<joelagnel> bluelightning, yeah. specially the bootloader environment files
etc make assumptions about the machine (i2c bus names etc)
<joelagnel> bluelightning, also Richard was suggesting that this was
attempted before but requires special mounts etc which is true
<joelagnel> we need it in there though so we could move it to the bsp for
now
<joelagnel> sounds good?
* Hoolxi (~Openfree@124.78.96.197) has joined #oe
<bluelightning> joelagnel: well as a temporary measure but really
duplicating class files is worth avoiding
<bluelightning> just because of the pain of keeping it up-to-date
<joelagnel> sure
<bluelightning> I have to admit I'm unsure of the correct solution in this
case though
<bluelightning> it's worth trying to coax people on the mailing list to come
up with the right answer :)
<joelagnel> bluelightning, sure will do ,thanks :)


Thanks,
Joel
Koen Kooi - Sept. 2, 2011, 4 p.m.
Why not start with

echo "inherit image" >> mynewclass.bbclass

And have the image inherit mynewclass?

Op 2 sep. 2011, om 17:44 heeft Joel A Fernandes het volgende geschreven:

> 
> 
> On Tue, Aug 30, 2011 at 12:47 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >
> > Op 30 aug. 2011, om 18:46 heeft Jason Kridner het volgende geschreven:
> >
> >> On Mon, Aug 29, 2011 at 7:08 PM, Joel A Fernandes <agnel.joel@gmail.com> wrote:
> >>> On Mon, Aug 29, 2011 at 4:03 PM, Jason Kridner <jkridner@beagleboard.org> wrote:
> >>>>>>>
> >>>>>>> This script is BSP specific and shouldn't live in the OE-core layer.
> >>>>>>
> >>>>>> The only issue is this script is used from within the IMAGE_CMD_sdimg
> >>>>>> code which lives in OE-core (meta/classes/image_types.
> >>>>>
> >>>>> classes shouldn't be calling external scripts
> >>>>>
> >>>>
> >>>> Is the right approach to add parameters to the IMAGE_CMD_sdimg class
> >>>> such that it can be used generically to produce SD card images,
> >>>> instead of trying to move this to meta-ti?  Should it perhaps be a bit
> >>>> closer to what is being done by the Linaro image tools [1]?
> >>>>
> >>>> [1] https://wiki.linaro.org/Source/ImageBuilding
> >>>>
> >>>
> >>> Don't the Linaro scripts need to run on the target?
> >>
> >> No.
> >>
> >>> Does it fit well
> >>> with OE(-core) ?
> >>
> >> I don't know, but I hoped that others would comment to help figure it
> >> out.  I think it is a common challenge not just for ARM architectures.
> >> I'm not sure if the approach is general enough or not, but it does go
> >> beyond the BeagleBoard.
> >>
> >> My primary concerns about leaving it in the BSP are:
> >> 1) that there is some room for non-BeagleBoard specific optimizations
> >> to the card layout and
> >> 2) there may be improvements to the tools that make it easier to
> >> create images for systems with different boot requirements.
> >>
> >> Also, I think we might want to move to an ext3 partition only in the
> >> future or other such layout optimizations.  I'd like that to be
> >> something that can be parameterized by the BSP.
> >
> > I think you're missing the point:
> >
> > The *script* needs to go into the BSP, you are free to extend the bbclasses with code to deal with sd cards internally in OE-core.
> >
> >
> 
> Hi Koen,
> 
> Can you suggest how we proceed with extending the bbclass?
> 
> I have tried both .bbappend and BBCLASSEXTEND and didn't get it to work.
> 
> I could create a new class and inherit the oe-core one from it with tweaks.
> 
> Here is complete IRC discussion between me and bluelightning on the reasoning to extend the image.bbclass:
> 
> * cminyard (~cminyard@pool-173-57-155-71.dllstx.fios.verizon.net) has joined #oe
> <joelagnel> I'd like to extend a bbclass in oe-core with tweaks in another layer
> <joelagnel> What is the right way to do so? .bbappend ? BBCLASSEXTEND?
> <GNUtoo|work> JaMa|Wrk, btw I've also another patch:
> <GNUtoo|work> at eukrea we use ubifs, and had the exact same issue than the freerunner ubifs issue, at least it seems
> <GNUtoo|work> we fixed it
> <GNUtoo|work> so if the patch arrived, it should fix it for you too
> <GNUtoo|work> joelagnel, BBCLASSEXTEND seem for recipes
> <joelagnel> I've seen it for classes in meta-oe:
> <joelagnel> ../meta-openembedded/meta-oe/classes/gnome.bbclass:BBCLASSEXTEND += "native"
> <joelagnel> GNUtoo|work, but it doesn't do what I want
> <joelagnel> I can create a new class, inherit from the oe-core one and put my code there, but I think that'll get rejected ;)
> <GNUtoo|work> ok
> <GNUtoo|work> maybe ask in the list
> <joelagnel> everyone here on long weekend holiday? ;)
> * hollisb (~hollisb@c-24-20-193-174.hsd1.or.comcast.net) has joined #oe
> <bluelightning> joelagnel: I don't think bbclassextend is what you want
> <bluelightning> what tweaks do you want to apply?
> <joelagnel> bluelightning, can I name a class in an upper layer with the same filename as that of a lower layer, and still be able to inherit the lower layer one?
> <bluelightning> I don't think you can do it that way no
> <bluelightning> if it's the same name it will just replace it effectively
> <bluelightning> the most likely result in that case is you'll get a circular reference
> <joelagnel> BlindMan, there was some talk about moving my changes (IMAGE_CMD_sdimg) to the bsp layer
> <joelagnel> https://github.com/joelagnel/oe-core/blob/db4c960da57e8e0ae4741eea703a4e163c589efa/meta/classes/image_types.bbclass
> <joelagnel> sorry I meant bluelightning ;)
> <joelagnel> need coffee!!! :-D
> <joelagnel> and need .bbclassappend ;)
> * msm (~msm@192.88.168.35) has joined #oe
> <bluelightning> hmm; this is an interesting one
> <bluelightning> I recall the discussion on the mailing list... I do wonder whether we ought to try to find a way to get this into oe-core itself
> * phdeswer has quit (Ping timeout: 276 seconds)
> <joelagnel> bluelightning, I'm copying in a ubi file into the rootfs which I don't think is generic enough
> <joelagnel> also all sorts of assumptions are made about bootloader file names (U-boot, uEnv, user.txt) etc
> <bluelightning> hmm
> <bluelightning> is this only likely to be applicable to one machine then?
> <joelagnel> bluelightning, yeah. specially the bootloader environment files etc make assumptions about the machine (i2c bus names etc)
> <joelagnel> bluelightning, also Richard was suggesting that this was attempted before but requires special mounts etc which is true
> <joelagnel> we need it in there though so we could move it to the bsp for now
> <joelagnel> sounds good?
> * Hoolxi (~Openfree@124.78.96.197) has joined #oe
> <bluelightning> joelagnel: well as a temporary measure but really duplicating class files is worth avoiding
> <bluelightning> just because of the pain of keeping it up-to-date
> <joelagnel> sure
> <bluelightning> I have to admit I'm unsure of the correct solution in this case though
> <bluelightning> it's worth trying to coax people on the mailing list to come up with the right answer :)
> <joelagnel> bluelightning, sure will do ,thanks :)
> 
> 
> Thanks,
> Joel
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Joel A Fernandes - Sept. 2, 2011, 6:12 p.m.
Hi Koen,

I thought of doing this, I just didn't know if it would be acceptable
and if there was a cleaner way of extending a .bbclass

Thanks,
Joel

On Fri, Sep 2, 2011 at 11:00 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> Why not start with
>
> echo "inherit image" >> mynewclass.bbclass
>
> And have the image inherit mynewclass?
>
> Op 2 sep. 2011, om 17:44 heeft Joel A Fernandes het volgende geschreven:
>
>>
>>
>> On Tue, Aug 30, 2011 at 12:47 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>> >
>> > Op 30 aug. 2011, om 18:46 heeft Jason Kridner het volgende geschreven:
>> >
>> >> On Mon, Aug 29, 2011 at 7:08 PM, Joel A Fernandes <agnel.joel@gmail.com> wrote:
>> >>> On Mon, Aug 29, 2011 at 4:03 PM, Jason Kridner <jkridner@beagleboard.org> wrote:
>> >>>>>>>
>> >>>>>>> This script is BSP specific and shouldn't live in the OE-core layer.
>> >>>>>>
>> >>>>>> The only issue is this script is used from within the IMAGE_CMD_sdimg
>> >>>>>> code which lives in OE-core (meta/classes/image_types.
>> >>>>>
>> >>>>> classes shouldn't be calling external scripts
>> >>>>>
>> >>>>
>> >>>> Is the right approach to add parameters to the IMAGE_CMD_sdimg class
>> >>>> such that it can be used generically to produce SD card images,
>> >>>> instead of trying to move this to meta-ti?  Should it perhaps be a bit
>> >>>> closer to what is being done by the Linaro image tools [1]?
>> >>>>
>> >>>> [1] https://wiki.linaro.org/Source/ImageBuilding
>> >>>>
>> >>>
>> >>> Don't the Linaro scripts need to run on the target?
>> >>
>> >> No.
>> >>
>> >>> Does it fit well
>> >>> with OE(-core) ?
>> >>
>> >> I don't know, but I hoped that others would comment to help figure it
>> >> out.  I think it is a common challenge not just for ARM architectures.
>> >> I'm not sure if the approach is general enough or not, but it does go
>> >> beyond the BeagleBoard.
>> >>
>> >> My primary concerns about leaving it in the BSP are:
>> >> 1) that there is some room for non-BeagleBoard specific optimizations
>> >> to the card layout and
>> >> 2) there may be improvements to the tools that make it easier to
>> >> create images for systems with different boot requirements.
>> >>
>> >> Also, I think we might want to move to an ext3 partition only in the
>> >> future or other such layout optimizations.  I'd like that to be
>> >> something that can be parameterized by the BSP.
>> >
>> > I think you're missing the point:
>> >
>> > The *script* needs to go into the BSP, you are free to extend the bbclasses with code to deal with sd cards internally in OE-core.
>> >
>> >
>>
>> Hi Koen,
>>
>> Can you suggest how we proceed with extending the bbclass?
>>
>> I have tried both .bbappend and BBCLASSEXTEND and didn't get it to work.
>>
>> I could create a new class and inherit the oe-core one from it with tweaks.
>>
>> Here is complete IRC discussion between me and bluelightning on the reasoning to extend the image.bbclass:
>>
>> * cminyard (~cminyard@pool-173-57-155-71.dllstx.fios.verizon.net) has joined #oe
>> <joelagnel> I'd like to extend a bbclass in oe-core with tweaks in another layer
>> <joelagnel> What is the right way to do so? .bbappend ? BBCLASSEXTEND?
>> <GNUtoo|work> JaMa|Wrk, btw I've also another patch:
>> <GNUtoo|work> at eukrea we use ubifs, and had the exact same issue than the freerunner ubifs issue, at least it seems
>> <GNUtoo|work> we fixed it
>> <GNUtoo|work> so if the patch arrived, it should fix it for you too
>> <GNUtoo|work> joelagnel, BBCLASSEXTEND seem for recipes
>> <joelagnel> I've seen it for classes in meta-oe:
>> <joelagnel> ../meta-openembedded/meta-oe/classes/gnome.bbclass:BBCLASSEXTEND += "native"
>> <joelagnel> GNUtoo|work, but it doesn't do what I want
>> <joelagnel> I can create a new class, inherit from the oe-core one and put my code there, but I think that'll get rejected ;)
>> <GNUtoo|work> ok
>> <GNUtoo|work> maybe ask in the list
>> <joelagnel> everyone here on long weekend holiday? ;)
>> * hollisb (~hollisb@c-24-20-193-174.hsd1.or.comcast.net) has joined #oe
>> <bluelightning> joelagnel: I don't think bbclassextend is what you want
>> <bluelightning> what tweaks do you want to apply?
>> <joelagnel> bluelightning, can I name a class in an upper layer with the same filename as that of a lower layer, and still be able to inherit the lower layer one?
>> <bluelightning> I don't think you can do it that way no
>> <bluelightning> if it's the same name it will just replace it effectively
>> <bluelightning> the most likely result in that case is you'll get a circular reference
>> <joelagnel> BlindMan, there was some talk about moving my changes (IMAGE_CMD_sdimg) to the bsp layer
>> <joelagnel> https://github.com/joelagnel/oe-core/blob/db4c960da57e8e0ae4741eea703a4e163c589efa/meta/classes/image_types.bbclass
>> <joelagnel> sorry I meant bluelightning ;)
>> <joelagnel> need coffee!!! :-D
>> <joelagnel> and need .bbclassappend ;)
>> * msm (~msm@192.88.168.35) has joined #oe
>> <bluelightning> hmm; this is an interesting one
>> <bluelightning> I recall the discussion on the mailing list... I do wonder whether we ought to try to find a way to get this into oe-core itself
>> * phdeswer has quit (Ping timeout: 276 seconds)
>> <joelagnel> bluelightning, I'm copying in a ubi file into the rootfs which I don't think is generic enough
>> <joelagnel> also all sorts of assumptions are made about bootloader file names (U-boot, uEnv, user.txt) etc
>> <bluelightning> hmm
>> <bluelightning> is this only likely to be applicable to one machine then?
>> <joelagnel> bluelightning, yeah. specially the bootloader environment files etc make assumptions about the machine (i2c bus names etc)
>> <joelagnel> bluelightning, also Richard was suggesting that this was attempted before but requires special mounts etc which is true
>> <joelagnel> we need it in there though so we could move it to the bsp for now
>> <joelagnel> sounds good?
>> * Hoolxi (~Openfree@124.78.96.197) has joined #oe
>> <bluelightning> joelagnel: well as a temporary measure but really duplicating class files is worth avoiding
>> <bluelightning> just because of the pain of keeping it up-to-date
>> <joelagnel> sure
>> <bluelightning> I have to admit I'm unsure of the correct solution in this case though
>> <bluelightning> it's worth trying to coax people on the mailing list to come up with the right answer :)
>> <joelagnel> bluelightning, sure will do ,thanks :)
>>
>>
>> Thanks,
>> Joel
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

Patch

diff --git a/meta/recipes-devtools/mkcard/mkcard-0.5/COPYING.patch b/meta/recipes-devtools/mkcard/mkcard-0.5/COPYING.patch
new file mode 100644
index 0000000..c70eaf6
--- /dev/null
+++ b/meta/recipes-devtools/mkcard/mkcard-0.5/COPYING.patch
@@ -0,0 +1,344 @@ 
+diff -ruN mkcard-0.5-orig/COPYING mkdcard-0.5/COPYING
+--- mkcard-0.5-orig/COPYING	1970-01-01 08:00:00.000000000 +0800
++++ mkcard-0.5/COPYING	2010-12-09 16:42:20.274984665 +0800
+@@ -0,0 +1,340 @@
++		    GNU GENERAL PUBLIC LICENSE
++		       Version 2, June 1991
++
++ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
++                       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
++ Everyone is permitted to copy and distribute verbatim copies
++ of this license document, but changing it is not allowed.
++
++			    Preamble
++
++  The licenses for most software are designed to take away your
++freedom to share and change it.  By contrast, the GNU General Public
++License is intended to guarantee your freedom to share and change free
++software--to make sure the software is free for all its users.  This
++General Public License applies to most of the Free Software
++Foundation's software and to any other program whose authors commit to
++using it.  (Some other Free Software Foundation software is covered by
++the GNU Library General Public License instead.)  You can apply it to
++your programs, too.
++
++  When we speak of free software, we are referring to freedom, not
++price.  Our General Public Licenses are designed to make sure that you
++have the freedom to distribute copies of free software (and charge for
++this service if you wish), that you receive source code or can get it
++if you want it, that you can change the software or use pieces of it
++in new free programs; and that you know you can do these things.
++
++  To protect your rights, we need to make restrictions that forbid
++anyone to deny you these rights or to ask you to surrender the rights.
++These restrictions translate to certain responsibilities for you if you
++distribute copies of the software, or if you modify it.
++
++  For example, if you distribute copies of such a program, whether
++gratis or for a fee, you must give the recipients all the rights that
++you have.  You must make sure that they, too, receive or can get the
++source code.  And you must show them these terms so they know their
++rights.
++
++  We protect your rights with two steps: (1) copyright the software, and
++(2) offer you this license which gives you legal permission to copy,
++distribute and/or modify the software.
++
++  Also, for each author's protection and ours, we want to make certain
++that everyone understands that there is no warranty for this free
++software.  If the software is modified by someone else and passed on, we
++want its recipients to know that what they have is not the original, so
++that any problems introduced by others will not reflect on the original
++authors' reputations.
++
++  Finally, any free program is threatened constantly by software
++patents.  We wish to avoid the danger that redistributors of a free
++program will individually obtain patent licenses, in effect making the
++program proprietary.  To prevent this, we have made it clear that any
++patent must be licensed for everyone's free use or not licensed at all.
++
++  The precise terms and conditions for copying, distribution and
++modification follow.
++
++		    GNU GENERAL PUBLIC LICENSE
++   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
++
++  0. This License applies to any program or other work which contains
++a notice placed by the copyright holder saying it may be distributed
++under the terms of this General Public License.  The "Program", below,
++refers to any such program or work, and a "work based on the Program"
++means either the Program or any derivative work under copyright law:
++that is to say, a work containing the Program or a portion of it,
++either verbatim or with modifications and/or translated into another
++language.  (Hereinafter, translation is included without limitation in
++the term "modification".)  Each licensee is addressed as "you".
++
++Activities other than copying, distribution and modification are not
++covered by this License; they are outside its scope.  The act of
++running the Program is not restricted, and the output from the Program
++is covered only if its contents constitute a work based on the
++Program (independent of having been made by running the Program).
++Whether that is true depends on what the Program does.
++
++  1. You may copy and distribute verbatim copies of the Program's
++source code as you receive it, in any medium, provided that you
++conspicuously and appropriately publish on each copy an appropriate
++copyright notice and disclaimer of warranty; keep intact all the
++notices that refer to this License and to the absence of any warranty;
++and give any other recipients of the Program a copy of this License
++along with the Program.
++
++You may charge a fee for the physical act of transferring a copy, and
++you may at your option offer warranty protection in exchange for a fee.
++
++  2. You may modify your copy or copies of the Program or any portion
++of it, thus forming a work based on the Program, and copy and
++distribute such modifications or work under the terms of Section 1
++above, provided that you also meet all of these conditions:
++
++    a) You must cause the modified files to carry prominent notices
++    stating that you changed the files and the date of any change.
++
++    b) You must cause any work that you distribute or publish, that in
++    whole or in part contains or is derived from the Program or any
++    part thereof, to be licensed as a whole at no charge to all third
++    parties under the terms of this License.
++
++    c) If the modified program normally reads commands interactively
++    when run, you must cause it, when started running for such
++    interactive use in the most ordinary way, to print or display an
++    announcement including an appropriate copyright notice and a
++    notice that there is no warranty (or else, saying that you provide
++    a warranty) and that users may redistribute the program under
++    these conditions, and telling the user how to view a copy of this
++    License.  (Exception: if the Program itself is interactive but
++    does not normally print such an announcement, your work based on
++    the Program is not required to print an announcement.)
++
++These requirements apply to the modified work as a whole.  If
++identifiable sections of that work are not derived from the Program,
++and can be reasonably considered independent and separate works in
++themselves, then this License, and its terms, do not apply to those
++sections when you distribute them as separate works.  But when you
++distribute the same sections as part of a whole which is a work based
++on the Program, the distribution of the whole must be on the terms of
++this License, whose permissions for other licensees extend to the
++entire whole, and thus to each and every part regardless of who wrote it.
++
++Thus, it is not the intent of this section to claim rights or contest
++your rights to work written entirely by you; rather, the intent is to
++exercise the right to control the distribution of derivative or
++collective works based on the Program.
++
++In addition, mere aggregation of another work not based on the Program
++with the Program (or with a work based on the Program) on a volume of
++a storage or distribution medium does not bring the other work under
++the scope of this License.
++
++  3. You may copy and distribute the Program (or a work based on it,
++under Section 2) in object code or executable form under the terms of
++Sections 1 and 2 above provided that you also do one of the following:
++
++    a) Accompany it with the complete corresponding machine-readable
++    source code, which must be distributed under the terms of Sections
++    1 and 2 above on a medium customarily used for software interchange; or,
++
++    b) Accompany it with a written offer, valid for at least three
++    years, to give any third party, for a charge no more than your
++    cost of physically performing source distribution, a complete
++    machine-readable copy of the corresponding source code, to be
++    distributed under the terms of Sections 1 and 2 above on a medium
++    customarily used for software interchange; or,
++
++    c) Accompany it with the information you received as to the offer
++    to distribute corresponding source code.  (This alternative is
++    allowed only for noncommercial distribution and only if you
++    received the program in object code or executable form with such
++    an offer, in accord with Subsection b above.)
++
++The source code for a work means the preferred form of the work for
++making modifications to it.  For an executable work, complete source
++code means all the source code for all modules it contains, plus any
++associated interface definition files, plus the scripts used to
++control compilation and installation of the executable.  However, as a
++special exception, the source code distributed need not include
++anything that is normally distributed (in either source or binary
++form) with the major components (compiler, kernel, and so on) of the
++operating system on which the executable runs, unless that component
++itself accompanies the executable.
++
++If distribution of executable or object code is made by offering
++access to copy from a designated place, then offering equivalent
++access to copy the source code from the same place counts as
++distribution of the source code, even though third parties are not
++compelled to copy the source along with the object code.
++
++  4. You may not copy, modify, sublicense, or distribute the Program
++except as expressly provided under this License.  Any attempt
++otherwise to copy, modify, sublicense or distribute the Program is
++void, and will automatically terminate your rights under this License.
++However, parties who have received copies, or rights, from you under
++this License will not have their licenses terminated so long as such
++parties remain in full compliance.
++
++  5. You are not required to accept this License, since you have not
++signed it.  However, nothing else grants you permission to modify or
++distribute the Program or its derivative works.  These actions are
++prohibited by law if you do not accept this License.  Therefore, by
++modifying or distributing the Program (or any work based on the
++Program), you indicate your acceptance of this License to do so, and
++all its terms and conditions for copying, distributing or modifying
++the Program or works based on it.
++
++  6. Each time you redistribute the Program (or any work based on the
++Program), the recipient automatically receives a license from the
++original licensor to copy, distribute or modify the Program subject to
++these terms and conditions.  You may not impose any further
++restrictions on the recipients' exercise of the rights granted herein.
++You are not responsible for enforcing compliance by third parties to
++this License.
++
++  7. If, as a consequence of a court judgment or allegation of patent
++infringement or for any other reason (not limited to patent issues),
++conditions are imposed on you (whether by court order, agreement or
++otherwise) that contradict the conditions of this License, they do not
++excuse you from the conditions of this License.  If you cannot
++distribute so as to satisfy simultaneously your obligations under this
++License and any other pertinent obligations, then as a consequence you
++may not distribute the Program at all.  For example, if a patent
++license would not permit royalty-free redistribution of the Program by
++all those who receive copies directly or indirectly through you, then
++the only way you could satisfy both it and this License would be to
++refrain entirely from distribution of the Program.
++
++If any portion of this section is held invalid or unenforceable under
++any particular circumstance, the balance of the section is intended to
++apply and the section as a whole is intended to apply in other
++circumstances.
++
++It is not the purpose of this section to induce you to infringe any
++patents or other property right claims or to contest validity of any
++such claims; this section has the sole purpose of protecting the
++integrity of the free software distribution system, which is
++implemented by public license practices.  Many people have made
++generous contributions to the wide range of software distributed
++through that system in reliance on consistent application of that
++system; it is up to the author/donor to decide if he or she is willing
++to distribute software through any other system and a licensee cannot
++impose that choice.
++
++This section is intended to make thoroughly clear what is believed to
++be a consequence of the rest of this License.
++
++  8. If the distribution and/or use of the Program is restricted in
++certain countries either by patents or by copyrighted interfaces, the
++original copyright holder who places the Program under this License
++may add an explicit geographical distribution limitation excluding
++those countries, so that distribution is permitted only in or among
++countries not thus excluded.  In such case, this License incorporates
++the limitation as if written in the body of this License.
++
++  9. The Free Software Foundation may publish revised and/or new versions
++of the General Public License from time to time.  Such new versions will
++be similar in spirit to the present version, but may differ in detail to
++address new problems or concerns.
++
++Each version is given a distinguishing version number.  If the Program
++specifies a version number of this License which applies to it and "any
++later version", you have the option of following the terms and conditions
++either of that version or of any later version published by the Free
++Software Foundation.  If the Program does not specify a version number of
++this License, you may choose any version ever published by the Free Software
++Foundation.
++
++  10. If you wish to incorporate parts of the Program into other free
++programs whose distribution conditions are different, write to the author
++to ask for permission.  For software which is copyrighted by the Free
++Software Foundation, write to the Free Software Foundation; we sometimes
++make exceptions for this.  Our decision will be guided by the two goals
++of preserving the free status of all derivatives of our free software and
++of promoting the sharing and reuse of software generally.
++
++			    NO WARRANTY
++
++  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
++FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
++OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
++PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
++OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
++MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
++TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
++PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
++REPAIR OR CORRECTION.
++
++  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
++WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
++REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
++INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
++OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
++TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
++YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
++PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
++POSSIBILITY OF SUCH DAMAGES.
++
++		     END OF TERMS AND CONDITIONS
++
++	    How to Apply These Terms to Your New Programs
++
++  If you develop a new program, and you want it to be of the greatest
++possible use to the public, the best way to achieve this is to make it
++free software which everyone can redistribute and change under these terms.
++
++  To do so, attach the following notices to the program.  It is safest
++to attach them to the start of each source file to most effectively
++convey the exclusion of warranty; and each file should have at least
++the "copyright" line and a pointer to where the full notice is found.
++
++    <one line to give the program's name and a brief idea of what it does.>
++    Copyright (C) <year>  <name of author>
++
++    This program is free software; you can redistribute it and/or modify
++    it under the terms of the GNU General Public License as published by
++    the Free Software Foundation; either version 2 of the License, or
++    (at your option) any later version.
++
++    This program is distributed in the hope that it will be useful,
++    but WITHOUT ANY WARRANTY; without even the implied warranty of
++    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
++    GNU General Public License for more details.
++
++    You should have received a copy of the GNU General Public License
++    along with this program; if not, write to the Free Software
++    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
++
++
++Also add information on how to contact you by electronic and paper mail.
++
++If the program is interactive, make it output a short notice like this
++when it starts in an interactive mode:
++
++    Gnomovision version 69, Copyright (C) year name of author
++    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
++    This is free software, and you are welcome to redistribute it
++    under certain conditions; type `show c' for details.
++
++The hypothetical commands `show w' and `show c' should show the appropriate
++parts of the General Public License.  Of course, the commands you use may
++be called something other than `show w' and `show c'; they could even be
++mouse-clicks or menu items--whatever suits your program.
++
++You should also get your employer (if you work as a programmer) or your
++school, if any, to sign a "copyright disclaimer" for the program, if
++necessary.  Here is a sample; alter the names:
++
++  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
++  `Gnomovision' (which makes passes at compilers) written by James Hacker.
++
++  <signature of Ty Coon>, 1 April 1989
++  Ty Coon, President of Vice
++
++This General Public License does not permit incorporating your program into
++proprietary programs.  If your program is a subroutine library, you may
++consider it more useful to permit linking proprietary applications with the
++library.  If this is what you want to do, use the GNU Library General
++Public License instead of this License.
diff --git a/meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt b/meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt
new file mode 100755
index 0000000..743b36d
--- /dev/null
+++ b/meta/recipes-devtools/mkcard/mkcard-0.5/mkcard.txt
@@ -0,0 +1,79 @@ 
+#! /bin/sh
+# mkcard.sh v0.5
+# (c) Copyright 2009 Graeme Gregory <dp@xora.org.uk>
+# Licensed under terms of GPLv2
+#
+# Parts of the procudure base on the work of Denys Dmytriyenko
+# http://wiki.omap.com/index.php/MMC_Boot_Format
+
+export LC_ALL=C
+
+if [ $# -ne 1 ]; then
+	echo "Usage: $0 <drive>"
+	exit 1;
+fi
+
+DRIVE=$1
+
+dd if=/dev/zero of=$DRIVE bs=1024 count=1024
+
+SIZE=`fdisk -l $DRIVE | grep Disk | grep bytes | awk '{print $5}'`
+
+echo DISK SIZE - $SIZE bytes
+
+CYLINDERS=`echo $SIZE/255/63/512 | bc`
+
+echo CYLINDERS - $CYLINDERS
+
+{
+echo ,9,0x0C,*
+echo ,,,-
+} | sfdisk -D -H 255 -S 63 -C $CYLINDERS $DRIVE
+
+sleep 1
+
+
+if [ -x `which kpartx` ]; then
+	kpartx -a ${DRIVE}
+fi
+
+# handle various device names.
+# note something like fdisk -l /dev/loop0 | egrep -E '^/dev' | cut -d' ' -f1 
+# won't work due to https://bugzilla.redhat.com/show_bug.cgi?id=649572
+
+PARTITION1=${DRIVE}1
+if [ ! -b ${PARTITION1} ]; then
+	PARTITION1=${DRIVE}p1
+fi
+
+DRIVE_NAME=`basename $DRIVE`
+DEV_DIR=`dirname $DRIVE`
+
+if [ ! -b ${PARTITION1} ]; then
+	PARTITION1=$DEV_DIR/mapper/${DRIVE_NAME}p1
+fi
+
+PARTITION2=${DRIVE}2
+if [ ! -b ${PARTITION2} ]; then
+	PARTITION2=${DRIVE}p2
+fi
+if [ ! -b ${PARTITION2} ]; then
+	PARTITION2=$DEV_DIR/mapper/${DRIVE_NAME}p2
+fi
+
+
+# now make partitions.
+if [ -b ${PARTITION1} ]; then
+	umount ${PARTITION1}
+	mkfs.vfat -F 32 -n "boot" ${PARTITION1}
+else
+	echo "Cant find boot partition in /dev"
+fi
+
+if [ -b ${PARITION2} ]; then
+	umount ${PARTITION2}
+	mke2fs -j -L "Angstrom" ${PARTITION2} 
+else
+	echo "Cant find rootfs partition in /dev"
+fi
+
diff --git a/meta/recipes-devtools/mkcard/mkcard_0.5.bb b/meta/recipes-devtools/mkcard/mkcard_0.5.bb
new file mode 100644
index 0000000..4d4a642
--- /dev/null
+++ b/meta/recipes-devtools/mkcard/mkcard_0.5.bb
@@ -0,0 +1,19 @@ 
+inherit native
+
+DESCRIPTION = "A tool to format SD Cards correctly"
+LICENSE = "GPLv2"
+LIC_FILES_CHKSUM = "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
+SECTION = "base"
+SRC_URI = "file://mkcard.txt \
+           file://COPYING.patch"
+PR = "r0"
+
+do_configure() {
+        install -m 0755 ${WORKDIR}/mkcard.txt ${S}/
+}
+
+do_install() {
+	install -d ${D}${base_sbindir}
+	install -m 0755 ${S}/mkcard.txt ${D}${base_sbindir}/mkcard
+}
+