Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sam9x5: fix ethernet pins in MII mode #1

Merged

Conversation

jgilles
Copy link

@jgilles jgilles commented Feb 12, 2013

The pins for emac0 were configured incorrectly for MII. This change correctly configures the pins as peripheral A.

@noglitch
Copy link
Member

Signed-off-by: Nicolas Ferre [email protected]

noglitch added a commit that referenced this pull request Feb 13, 2013
sam9x5: fix ethernet pins in MII mode
@noglitch noglitch merged commit 55eba57 into linux4sam:u-boot-2012.10-at91 Feb 13, 2013
voiceshen pushed a commit that referenced this pull request Sep 11, 2014
Since B&R boards uses only MMC-Controller #1, it only
wastes time if we initialize #0 first to see that there is nothing.

Cc: <[email protected]>
Acked-by: Pantelis Antoniou <[email protected]>
Signed-off-by: Hannes Petermaier <[email protected]>
JoshWu added a commit that referenced this pull request Sep 11, 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 #1.

Refer to the commit: 10a37fd for details of device & partition string.

Signed-off-by: Josh Wu <[email protected]>
Reviewed-by: Stephen Warren <[email protected]>
adamfeuer pushed a commit to adamfeuer/u-boot-at91 that referenced this pull request Aug 19, 2020
After updating libavb to most recent version from AOSP/master, two new
warnings appear:

Warning linux4sam#1:

    lib/libavb/avb_cmdline.c: In function 'avb_append_options':
    lib/libavb/avb_cmdline.c:365:15: warning: 'dm_verity_mode' may be
                                     used uninitialized in this function
                                     [-Wmaybe-uninitialized]
         new_ret = avb_replace(
                   ^~~~~~~~~~~~
             slot_data->cmdline, "$(ANDROID_VERITY_MODE)", dm_verity_mode);
             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    lib/libavb/avb_cmdline.c:374:8: warning: 'verity_mode' may be used
                                    uninitialized in this function
                                    [-Wmaybe-uninitialized]
       if (!cmdline_append_option(
            ^~~~~~~~~~~~~~~~~~~~~~
               slot_data, "androidboot.veritymode", verity_mode)) {
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Warning linux4sam#2:

    lib/libavb/avb_slot_verify.c: In function 'avb_slot_verify':
    lib/libavb/avb_slot_verify.c:1349:23: warning: 'ret' may be used
                                          uninitialized in this function
                                          [-Wmaybe-uninitialized]
       AvbSlotVerifyResult ret;
                           ^~~

Fix those by providing default return values to affected functions.

Signed-off-by: Sam Protsenko <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants