- Oct 18, 2007
-
-
Tony Li authored
Correct to val8 from val. Signed-off-by:
Tony Li <tony.li@freescale.com> Signed-off-by:
Kim Phillips <kim.phillips@freescale.com>
-
git://www.denx.de/git/u-bootKim Phillips authored
-
- Oct 16, 2007
-
-
Jon Loeliger authored
As a direct correlation exists between DDR DIMM slots and SPD EEPROM addresses used to configure them, use the individually defined SPD_EEPROM_ADDRESS* values to determine if a DDR DIMM slot should have its SPD configuration read or not. Effectively, this now allows for 1 or 2 DIMM slots per memory controller. Signed-off-by:
Jon Loeliger <jdl@freescale.com>
- Oct 15, 2007
-
-
Wolfgang Denk authored
-
Rodolfo Giometti authored
Some USB keys need to be switched off before loading the kernel otherwise they can remain in an undefined status which prevents them to be correctly recognized by the kernel. Signed-off-by:
Rodolfo Giometti <giometti@linux.it>
-
Stefan Roese authored
The I2C bootstrap values that can be setup via the "bootstrap" command, were setup incorrect regarding the generation of the internal sync PCI clock. The values for PLB clock == 133MHz were slighly incorrect and the values for PLB clock == 166MHz were totally incorrect. This could lead to a hangup upon booting while PCI configuration scan. This patch fixes this issue and configures valid PCI divisor values for the sync PCI clock, with respect to the provided external async PCI frequency. Here the values of the formula in the chapter 14.2 "PCI clocking" from the 440EPx users manual: AsyncPCICLK - 1MHz <= SyncPCIClk <= (2 * AsyncPCIClk) - 1MHz 33MHz async PCI frequency: PLB = 133: => 32 <= 44.3 <= 65 (div = 3) PLB = 166: => 32 <= 55.3 <= 65 (div = 3) 66MHz async PCI frequency: PLB = 133: => 65 <= 66.5 <= 132 (div = 2) PLB = 166: => 65 <= 83 <= 132 (div = 2) Signed-off-by:
Stefan Roese <sr@denx.de>
-
Stefan Roese authored
The BCSR status bit for the 66MHz PCI operation was correctly addressed (MSB/LSB problem). Now the correct currently setup PCI frequency is displayed upon bootup. This patch also fixes this problem on Rainier & Yellowstone, since these boards use the same souce code as Sequoia & Yosemite do. Signed-off-by:
Stefan Roese <sr@denx.de>
-
- Oct 14, 2007
-
-
Michal Simek authored
and remove code violation
-
git://www.denx.de/git/u-bootMichal Simek authored
-
Michal Simek authored
-
- Oct 13, 2007
-
-
Wolfgang Denk authored
Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
Jean-Christophe PLAGNIOL-VILLARD authored
Signed-off-by:
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
-
Wolfgang Denk authored
Signed-off-by:
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
Wolfgang Denk authored
Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
- Oct 12, 2007
-
-
Wolfgang Denk authored
Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
- Oct 10, 2007
-
-
Wolfgang Denk authored
-
Wolfgang Denk authored
-
Wolfgang Denk authored
-
- Oct 09, 2007
-
-
Grzegorz Bernacki authored
Signed-off-by:
Grzegorz Bernacki <gjb@semihalf.com>
-
- Oct 06, 2007
-
-
Haavard Skinnemoen authored
The ATSTK1000-specific flash driver intializes bi_flashstart, bi_flashsize and bi_flashoffset, but other flash drivers, like the CFI driver, don't. Initialize these in board_init_r instead so that things will still be set up correctly when we switch to the CFI driver. Signed-off-by:
Haavard Skinnemoen <hskinnemoen@atmel.com>
-
- Oct 05, 2007
-
-
Marian Balakowicz authored
Signed-off-by:
Marian Balakowicz <m8@semihalf.com>
-
Bartlomiej Sieka authored
Signed-off-by:
Bartlomiej Sieka <tur@semihalf.com>
-
- Oct 04, 2007
-
- Oct 02, 2007
-
-
Haavard Skinnemoen authored
CFG_MEMTEST_START uses weird magic involving gd, which fails to compile. Use hardcoded values instead (we actually know how much RAM we have on board.) Signed-off-by:
Haavard Skinnemoen <hskinnemoen@atmel.com>
-
Haavard Skinnemoen authored
-
Stefan Roese authored
Signed-off-by:
Stefan Roese <sr@denx.de>
-
Stefan Roese authored
Signed-off-by:
Stefan Roese <sr@denx.de>
-
Grzegorz Bernacki authored
EPLD forces modes of PHY operation. By default full duplex is turned off. This fix turns it on. Signed-off-by:
Grzegorz Bernacki <gjb@semihalf.com>
-
Timo Ketola authored
Original isp116x-hcd code prepared multiple PTDs for longer than 16 byte transfers for one endpoint. That is unnecessary because the ISP116x is able to split long data from one PTD into multiple transactions based on the buffer size of the endpoint. It also caused serious problems if the endpoint NAKed some of the transactions. In that case ISP116x wouldn't notice that the other PTDs were for the same endpoint and would try the other PTDs possibly out of order. That would break the whole transfer. This patch makes isp116x_submit_job to use one PTD for one transfer. Signed-off-by:
Timo Ketola <timo.ketola@exertus.fi> Signed-off-by:
Markus Klotzbuecher <mk@denx.de>
-
- Sep 27, 2007
-
-
Jean-Christophe PLAGNIOL-VILLARD authored
Signed-off-by:
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
-
Stefan Roese authored
-