- 12 4月, 2019 24 次提交
-
-
由 Philippe Reynes 提交于
As no gpio.h is defined for this architecture, to avoid a compilation failure, do not include <asm/arch/gpio.h> for arch bcm63158. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
This IP is also used on some arm SoC, so we allow to use this driver on arch bcm63158. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
Enable the gpio support (driver and command) in the configuration of the board bcm968580xref. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
Enable all the gpio controllers in the device tree of the board bcm968580xref. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
Add 8 gpio controllers in the bcm6858 device tree. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
As no gpio.h is defined for this architecture, to avoid compilation failure, do not include <asm/arch/gpio.h> for arch bcm6858. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
This IP is also used on some arm SoC, so we allow to use this driver on arch bcm6858. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
Enable the gpio support (driver and command) in the configuration of the board bcm968380gerg Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
Enable the gpio controllers in the device tree of the board bcm968380gerg. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com> Reviewed-by: NDaniel Schwierzeck <daniel.schwierzeck@gmail.com>
-
由 Philippe Reynes 提交于
Add gpio controllers in bcm6838 device tree. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com> Reviewed-by: NDaniel Schwierzeck <daniel.schwierzeck@gmail.com>
-
由 Philippe Reynes 提交于
This driver is used on several big endian mips board. So we could use raw I/O function instead of forcing big endian access. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com> Reviewed-by: NDaniel Schwierzeck <daniel.schwierzeck@gmail.com>
-
由 Rosy Song 提交于
S17 ethernet support is for QCA8337N, which used on AP152 (QCA9563) board. It is a 7 ports GbE switch. Signed-off-by: NRosy Song <rosysong@rosinson.com> Changes for v2-v3: - add more commit message for s17 Changes for v4-v5: - coding style cleanup
-
由 Rosy Song 提交于
QCA9563 is CPU used on AP152 board : Clock speed : 750 MHz , Arch : Mips 74Kc, Eth : SGMII interface, MIMO config : 3 * 3 450M, 2 * USB 2.0, Signed-off-by: NRosy Song <rosysong@rosinson.com> Changes for v2: - coding style cleanup - remove ununsed flash chip in defconfig - enable automatic icache / dcache size in defconfig Changes for v3: - add detailed information for qca956x in commit message Changes for v4: - remove pre-configured network settings in ap152.h Changes for v5: - coding style cleanup
-
由 Rosy Song 提交于
See details in chapter 8.6.2 and 8.6.4 (page 140-141) of qca9563 datasheet, NFRAC[17:0] So the mask of [17:5] is 0x1fff not 0x3fff. Signed-off-by: NRosy Song <rosysong@rosinson.com> Changes for v2-v3: - add more information for this commit Changes for v4-v5: - coding style cleanup
-
由 Álvaro Fernández Rojas 提交于
This patch prevents errors when running tftpput. Signed-off-by: NÁlvaro Fernández Rojas <noltari@gmail.com>
-
由 Horatiu Vultur 提交于
The function mscc_miim_reset resets all the phys, but it is called for each phy separetely. One consequence of this is that the boot time is increased by 2 seconds. The fix consists for calling the mscc_miim_reset function only once for all phys. Signed-off-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NDaniel Schwierzeck <daniel.schwierzeck@gmail.com>
-
由 Horatiu Vultur 提交于
Remove the function boot_reloc_ramdisk in the file arch/mips/lib/bootm because it is relocating again the ramdisk. The function do_bootm_states() already relocates the ramdisk even if it is a legacy uImage or a FIT image. The relocation in the function do_bootm_states() was introduce in the commit c2e7e72b ("bootm: relocate ramdisk if CONFIG_SYS_BOOT_RAMDISK_HIGH set") Signed-off-by: NHoratiu Vultur <horatiu.vultur@microchip.com> Reviewed-by: NDaniel Schwierzeck <daniel.schwierzeck@gmail.com>
-
由 Stefan Roese 提交于
This patch changes Gardena to the correct GARDENA spelling. Also the platform name is "GARDENA smart Gateway". This patch changes the incorrect occurrances. Signed-off-by: NStefan Roese <sr@denx.de> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
-
由 Stefan Roese 提交于
The new mtd is very useful so let's enable it on the LinkIt Smart 7688 as well. Signed-off-by: NStefan Roese <sr@denx.de> Cc: Jiri Kastner <cz172638@gmail.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
-
由 Rosy Song 提交于
Signed-off-by: NRosy Song <rosysong@rosinson.com>
-
由 Rosy Song 提交于
Signed-off-by: NRosy Song <rosysong@rosinson.com>
-
由 Rosy Song 提交于
Signed-off-by: NRosy Song <rosysong@rosinson.com>
-
-
-
- 10 4月, 2019 16 次提交
-
-
由 Tom Rini 提交于
- test.py tests for mmc - ext4 symlink support and other fixes - ext4 block group descriptor sizing
-
由 Tom Rini 提交于
Currently enabling fsck on FAT16/FAT32 exposes that we have problems with: TestFsBasic.test_fs13[fat16] TestFsBasic.test_fs11[fat32] TestFsBasic.test_fs12[fat32] TestFsBasic.test_fs13[fat32] TestFsExt.test_fs_ext1[fat32] TestFsExt.test_fs_ext2[fat32] TestFsExt.test_fs_ext3[fat32] TestFsExt.test_fs_ext4[fat32] TestFsExt.test_fs_ext5[fat32] TestFsExt.test_fs_ext6[fat32] TestFsExt.test_fs_ext7[fat32] TestFsExt.test_fs_ext8[fat32] TestFsExt.test_fs_ext9[fat32] TestMkdir.test_mkdir6[fat16] TestMkdir.test_mkdir1[fat32] TestMkdir.test_mkdir2[fat32] TestMkdir.test_mkdir3[fat32] TestMkdir.test_mkdir4[fat32] TestMkdir.test_mkdir5[fat32] TestMkdir.test_mkdir6[fat32] TestUnlink.test_unlink1[fat16] TestUnlink.test_unlink2[fat16] TestUnlink.test_unlink3[fat16] TestUnlink.test_unlink4[fat16] TestUnlink.test_unlink5[fat16] TestUnlink.test_unlink6[fat16] TestUnlink.test_unlink7[fat16] TestUnlink.test_unlink1[fat32] TestUnlink.test_unlink2[fat32] TestUnlink.test_unlink3[fat32] TestUnlink.test_unlink4[fat32] TestUnlink.test_unlink5[fat32] TestUnlink.test_unlink6[fat32] TestUnlink.test_unlink7[fat32] This is because we don't update the "information sector" on FAT32. While in the future we should resolve this problem and include that feature, we should enable fsck for ext4 to ensure that things remain in good shape there. Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Benjamin Lim 提交于
Ext4 allows for arbitrarily sized block group descriptors when 64-bit addressing is enabled, which was previously not properly supported. This patch dynamically allocates a chunk of memory of the correct size. Signed-off-by: NBenjamin Lim <jarsp.ctf@gmail.com>
-
由 Marek Vasut 提交于
Add option to the mmc rd test to check the duration of the execution of the mmc read command. This allows intercepting read performance regressions. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Tom Rini <trini@konsulko.com> Cc: Simon Glass <sjg@chromium.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Marek Vasut 提交于
Add test for 'mmc info' subcommand. This tests whether the card information is obtained correctly and verifies the device, bus speed, bus mode and bus width. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Tom Rini <trini@konsulko.com> Cc: Simon Glass <sjg@chromium.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Marek Vasut 提交于
Add test for 'mmc rescan' subcommand. This tests whether the system can switch to a specific card and then rescan the card. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Tom Rini <trini@konsulko.com> Cc: Simon Glass <sjg@chromium.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Marek Vasut 提交于
Add separate test for 'mmc dev' subcommand. This tests whether the system can switch to a specific card. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Tom Rini <trini@konsulko.com> Cc: Simon Glass <sjg@chromium.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Marek Vasut 提交于
Factor out the 'mmc dev' call so it can be recycled by other tests. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Tom Rini <trini@konsulko.com> Cc: Simon Glass <sjg@chromium.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Anssi Hannula 提交于
A FAT12/FAT16 root directory location is specified by a sector offset and it might not start at a cluster boundary. It also resides before the data area (before cluster 2). However, the current code assumes that the root directory is located at a beginning of a cluster, causing no files to be found if that is not the case. Since the FAT12/FAT16 root directory is located before the data area and is not aligned to clusters, using unsigned cluster numbers to refer to the root directory does not work well (the "cluster number" may be negative, and even allowing it be signed would not make it properly aligned). Modify the code to not use the normal cluster numbering when referring to the root directory of FAT12/FAT16 and instead use a cluster-sized offsets counted from the root directory start sector. This is a relatively common case as at least the filesystem formatter on Win7 seems to create such filesystems by default on 2GB USB sticks when "FAT" is selected (cluster size 64 sectors, rootdir size 32 sectors, rootdir starts at half a cluster before cluster 2). dosfstools mkfs.vfat does not seem to create affected filesystems. Signed-off-by: NAnssi Hannula <anssi.hannula@bitwise.fi> Reviewed-by: NBernhard Messerklinger <bernhard.messerklinger@br-automation.com> Tested-by: NBernhard Messerklinger <bernhard.messerklinger@br-automation.com>
-
由 Gero Schumacher 提交于
Hi, when I try to load a sparse file via ext4load, I am getting the error message 'invalid extent' After a deeper look in the code, it seems to be an issue in the function ext4fs_get_extent_block in fs/ext4/ext4_common.c: The file starts with 1k of zeros. The blocksize is 1024. So the first extend block contains the following information: eh_entries: 1 eh_depth: 1 ei_block 1 When the upper layer (ext4fs_read_file) asks for fileblock 0, we are running in the 'invalid extent' error message. For me it seems, that the code is not prepared for handling a sparse block at the beginning of the file. The following change, solved my problem: I am really not an expert in ext4 filesystems. Can somebody please have a look at this issue and give me a feedback, if I am totally wrong or not?
-
由 Jean-Jacques Hiblot 提交于
Test cases are: 1) basic link creation, verify it can be followed 2) chained links, verify it can be followed 3) replace exiting file a with a link, and a link with a link. verify it can be followed 4) create a broken link, verify it can't be followed Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Jean-Jacques Hiblot 提交于
The command line is: ln <interface> <dev[:part]> target linkname Currently symbolic links are supported only in ext4 and only if the option CMD_EXT4_WRITE is enabled. Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Jean-Jacques Hiblot 提交于
Re-use the functions used to write/create a file, to support creation of a symbolic link. The difference with a regular file are small: - The inode mode is flagged with S_IFLNK instead of S_IFREG - The ext2_dirent's filetype is FILETYPE_SYMLINK instead of FILETYPE_REG - Instead of storing the content of a file in allocated blocks, the path to the target is stored. And if the target's path is short enough, no block is allocated and the target's path is stored in ext2_inode.b.symlink As with regulars files, if a file/symlink with the same name exits, it is unlinked first and then re-created. Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> [trini: Fix ext4 env code] Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Jean-Jacques Hiblot 提交于
There is no need to modify the buffer passed to ext4fs_write_file(). The memset() call is not required here and was likely copied from the equivalent part of the ext4fs_read_file() function where we do need it. Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Jean-Jacques Hiblot 提交于
We need to make sure that file writes,file creation, etc. are properly performed and do not corrupt the filesystem. To help with this, introduce the assert_fs_integrity() function that executes the appropriate fsck tool. It should be called at the end of any test that modify the content/organization of the filesystem. Currently only supports FATs and EXT4. Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Jean-Jacques Hiblot 提交于
If the metadata checksums are enabled, all write operations will fail. Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-