From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Fri, 04 Oct 2013 17:31:18 +0200 Subject: [Buildroot] [PATCHv2] beaglebone: add BeagleBone Black support In-Reply-To: <1380522195.4232.2.camel@viko> ("Fatih =?utf-8?B?QcWfxLFjxLEi?= =?utf-8?B?J3M=?= message of "Mon, 30 Sep 2013 09:23:15 +0300") References: <1380220826-17732-1-git-send-email-jkridner@beagleboard.org> <1380337717-19697-1-git-send-email-jkridner@beagleboard.org> <1380522195.4232.2.camel@viko> Message-ID: <87fvshjbnd.fsf@dell.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Fatih" == Fatih A??c? writes: Fatih> On Sat, 2013-09-28 at 03:08 +0000, Jason Kridner wrote: >> From: Jason Kridner >> >> * Configure as initramfs >> * Update BeagleBone to 3.8.13-beagleboard kernel >> * Update to u-boot 2013.07 >> * Add BeagleBone Black device tree >> >> Changes since v1 (http://lists.busybox.net/pipermail/buildroot/2013-September/079046.html): >> * Added BeagleBone Black to single config for BeagleBone and BeagleBone Black, >> rather than having two configs >> * Used 'make ARCH=arm savedefconfig' to create Linux config file >> * Dropped setting of DEVTMPFS, since it is default now >> * Switched to u-boot 2013.07 from 2013.04 >> * Patched u-boot to work with initramfs by default without uEnv.txt >> * Removed wake-up M3 firmware loading for now, until debugged I don't seem to have received the original here (probably because of my mail problems), but what's the reason for the ext2 -> initramfs changes? -- Bye, Peter Korsgaard