Open
Conversation
There has been interest to overhaul development on the Amazon Otter and I'd like to contribute for it, Hashcode had recently posted some mockups of an improved bootlogo and I'd want to improve on it This pull request includes UBoot splashes for the Fastboot, Low Battery and Init splash screens I have not found documentation to create a U-Boot friendly compressed rle image so these are on uncompressed rle format (I couldn't even look at them to take a look at the orientation so this is completly untested, fastboot is unlinked)
Hashcode
pushed a commit
to Hashcode/u-boot
that referenced
this pull request
Sep 28, 2014
Since B&R boards uses only MMC-Controller KFire-Android#1, it only wastes time if we initialize #0 first to see that there is nothing. Cc: <trini@ti.com> Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com> Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
Hashcode
pushed a commit
to Hashcode/u-boot
that referenced
this pull request
Sep 28, 2014
Use get_device_and_partition() is better since: 1. It will call the device initialize function internally. So we can remove the mmc intialization code to save many lines. 2. It is used by fatls/fatload/fatwrite. So saveenv & load env should use it too. 3. It can parse the "D:P", "D", "D:", "D:auto" string to get correct device and partition information by run-time. Also we remove the FAT_ENV_DEVICE and FAT_ENV_PART. We use a string: FAT_ENV_DEVICE_AND_PART. For at91sam9m10g45ek, it is "0". That means use device 0 and if: a)device 0 has no partition table, use the whole device as a FAT file system. b)device 0 has partittion table, use the partition KFire-Android#1. Refer to the commit: 10a37fd for details of device & partition string. Signed-off-by: Josh Wu <josh.wu@atmel.com> Reviewed-by: Stephen Warren <swarren@nvidia.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There has been interest to overhaul development on the Amazon Otter and
I'd like to contribute for it, Hashcode had recently posted some mockups
of an improved bootlogo and I'd want to improve on it
This pull request includes UBoot splashes for the Fastboot, Low Battery
and Init splash screens
I have not found documentation to create a U-Boot friendly compressed
rle image so these are on uncompressed rle format (I couldn't even look
at them to take a look at the orientation so this is completly untested,
fastboot is unlinked)