This patch adds an option to skip the video initialization on for all
video drivers. This is needed for the CPCI750 which can be built as CPCI
host and adapter/target board. And the adapter board can't access the
video cards located on the CompactPCI bus.
Signed-off-by: Stefan Roese
Cc: Anatolij
On Friday 15 May 2009 07:36:33 Wolfgang Denk wrote:
> > i suggest to move the board_video_skip() to the top of
> > drv_video_init() in drivers/video/cfb_console.c.
> >
> > What are the arguments against doing it?
>
> Not from my side.
OK, I'll post a new patch in a short while.
Thanks.
Best rega
Dear Anatolij Gustschin,
In message <4a0cbb03.9040...@denx.de> you wrote:
>
> i suggest to move the board_video_skip() to the top of
> drv_video_init() in drivers/video/cfb_console.c.
>
> What are the arguments against doing it?
Not from my side.
Best regards,
Wolfgang Denk
--
DENX Software
Hi Wolfgang,
On Thursday 14 May 2009 22:59:49 Wolfgang Denk wrote:
> Commit 574b319512 introduced a subtle bug by mixing a list of tests
> for "dev_desc->type" and "dev_desc->if_type" into one switch(), which
> then mostly did not work because "dev_desc->type" cannot take any
> "IF_*" type values.
Hi Wolfgang,
On Thursday 14 May 2009 23:18:35 Wolfgang Denk wrote:
> Also enable display of 'E'mpty sectors in "lsinfo" output.
s lsinfo/flinfo.
Best regards,
Stefan
=
DENX Software Engineering GmbH, MD: Wolfgang Denk & Det
The BCSR17[7] = 1 will unlock the write protect of FLASH.
The WP# pin only controls the write protect of top/bottom sector,
That is why we can save env, but we can't write the first sector
before the patch.
Signed-off-by: Dave Liu
---
board/freescale/mpc8569mds/bcsr.c |2 +-
1 files changed,
> Interesting. I've tried to use your patch but still hanging
> board_init_f.
> Even putting BOOKE_PAGESZ_256M in set_tlb the problem occur.
Because you are using the 8548 with e500v2 core, so the bug doesn't
effect your board when you are using the 1G DIMMs.
_
> > The tlb settings looks fine (debbug in setup_ddr_tlbs()):
> >
> > ram_tlb_address: 0x0, ram_tlb_address: 0x0, ram_tlb_index:
> 0x8, tlb_size:
> 0xa
> > ram_tlb_address: 0x4000, ram_tlb_address: 0x4000,
> ram_tlb_index:
> 0x9, tlb_size: 0xa
>
> "tlb_size: 0xa" is _not_ fine.
>
No,
> my mpc8572ds (2x 512 MiB ram) had initially u-boot 1.3.0-rc2 and I
> haven't notice any problems. Today I updated u-boot to
> v2009.03 because
> I was not able to boot current vanilla linux kernel in smp mode.
> Since then I experience random kernel opses. I thing it has
> something to
> do wit
Stefan Roese wrote:
> On Thursday 14 May 2009 17:01:46 Wolfgang Denk wrote:
If this should be the highest level in the call chain, then any
conditional calling should be done here.
>>> OK, I can move the conditional calling to this level.
>> I'm not sure.
>>
But - don't we alr
Hello Wolfgang, Stefan,
Wolfgang Denk wrote:
> In message <200905141613.20127...@denx.de> you wrote:
>>> If this should be the highest level in the call chain, then any
>>> conditional calling should be done here.
>> OK, I can move the conditional calling to this level.
>
> I'm not sure.
> I'm working on a mpc85xx board very similar to MPC8548CDS. I
> have 2 DIMMs and each one with it own spd eeprom and with
> only one chip select (cs0 and cs2). I'm trying to use two 1Gb
> DDR2s. My ddr configurations:
>
> /* DDR Setup */
> #define CONFIG_VERY_BIG_RAM
> #define CONFIG_FSL_DDR2
> I have a custom board similar to MPC8560ADS board with 1GB
> DDR SDRAM. The DDR SDRAM Make
> is MT18VDDF12872DG-335D3. In U-BOOT (2009.01) config file I
> have enabled CONFIG_SPD_EEPROM
> so U-boot configures MPC8560ADS DDR controller with the
> values read from SPD_EEPROM (i2c
> address 0x51)
Hi Alfred,
alfred steele wrote:
>> We don't have clocks API in U-Boot. You need to enable the clock by
>> setting appropriate bit in the clocks control register manually.
>>
> Why do i have to touch the CCM? IIRC, Can't it be controlled with the
> STR_STP_CLOCK (bit 0). When i read the CCM u
Hi,
> my English is not perfect really... but I'm actually having hard times
> trying to understand yours... So I give you my excuses in advance for
> possible misunderstandings...
IMO too, I know i have a horrible English . Trying to improve;) Pls
dont hesitate in asking em to rephrase.
> I beli
Several boards used different ways to specify the size of the
protected area when enabling flash write protection for the sectors
holding the environment variables: some used CONFIG_ENV_SIZE and
CONFIG_ENV_SIZE_REDUND, some used CONFIG_ENV_SECT_SIZE, and some even
a mix of both for the "normal" and
Remove "saveenv" from "update" definition: the environment is outside
the U-Boot image on TQM85xx and therefor not affected by updates.
Also "beautify" code a bit (vertical alignment).
Signed-off-by: Wolfgang Denk
---
include/configs/TQM85xx.h |7 +++
1 files changed, 3 insertions(+), 4
Old TQM85xx boards had 'M' type Spansion Flashes from the S29GLxxxM
series while new boards have 'N' type Flashes from the S29GLxxxN
series, which have bigger sectors: 2 x 128 instead of 2 x 64 KB.
We now change the configuration to the new flash types for all
boards; this also works on old boards
Dear "Cote, Sylvain",
I re-added the mailing list, as others might be interested, too.
Also, please don't top post / full quore. Please read
http://www.netmeister.org/news/learn2quote.html
In message
<579b119545daef4689c8fbeefec5793f01d4fdf6e...@atlmbx.verint.corp.verintsystems.com>
you wrote
Signed-off-by: Wolfgang Denk
---
board/tqc/tqm834x/pci.c | 45
board/tqc/tqm834x/tqm834x.c | 11
include/configs/TQM834x.h | 59 --
3 files changed, 95 insertions(+), 20 deletions(-)
diff --git a/board/
Also reserve more space for U-Boot as it will probably grow soon.
Signed-off-by: Wolfgang Denk
---
include/configs/TQM834x.h | 26 --
1 files changed, 12 insertions(+), 14 deletions(-)
diff --git a/include/configs/TQM834x.h b/include/configs/TQM834x.h
index b74b404..0c
Also enable display of 'E'mpty sectors in "lsinfo" output.
Signed-off-by: Wolfgang Denk
---
include/configs/TQM834x.h |7 +++
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/include/configs/TQM834x.h b/include/configs/TQM834x.h
index 5590d2e..c504ecb 100644
--- a/include/c
The following 3 patches update the configuration for the TQM834x
board:
Wolfgang Denk (3):
TQM834x: fix environment size; add redundant env.
TQM834x: add FDT support
TQM834x: use buffered writes to accelerate writing to flash
Signed-off-by: Wolfgang Denk
___
Hi Alfred,
my English is not perfect really... but I'm actually having hard times
trying to understand yours... So I give you my excuses in advance for
possible misunderstandings...
alfred steele wrote:
> Looks like accidently somehow pressed the send button. Apologize!
>
> Thanks for the much a
Commit 574b319512 introduced a subtle bug by mixing a list of tests
for "dev_desc->type" and "dev_desc->if_type" into one switch(), which
then mostly did not work because "dev_desc->type" cannot take any
"IF_*" type values. A later fix in commit 8ec6e332ea changed the
switch() into testing "dev_des
Commit 574b319512 introduced a subtle bug by mixing a list of tests
for "dev_desc->type" and "dev_desc->if_type" into one switch(), which
then mostly did not work because "dev_desc->type" cannot take any
"IF_*" type values. A later fix in commit 8ec6e332ea changed the
switch() into testing "dev_des
Dear Stefan Roese,
In message <200905141714.34154...@denx.de> you wrote:
>
> > U-Boot 1.3.2-rc2-g02e4b4e3 (Feb 28 2008 - 16:46:26)
> ^
> That's very old.
Indeed. That's why I included this information as data point.
> From my understanding this worked at some point on the CPCI750 a
Looks like accidently somehow pressed the send button. Apologize!
Thanks for the much awaited reply.
> I've only tried my patch on i.MX27 board. I mentioned that it may work
> on MX3's too cause the kernel driver used as a source works on both MX2
> and MX3. You need to do some changes for my dr
Thanks for the much waited reply.
> I've only tried my patch on i.MX27 board. I mentioned that it may work
> on MX3's too cause the kernel driver used as a source works on both MX2
> and MX3. You need to do some changes for my driver to work on MX3. Check
> the pins configuration and if you have M
Dear "Cote, Sylvain",
In message
<579b119545daef4689c8fbeefec5793f01d4fdf6e...@atlmbx.verint.corp.verintsystems.com>
you wrote:
>
> I am currently working on AMCC Kilauea eval board. I am using u-boot
> 2009.3. I boot my board from nand. By default, when booting from
> nand, the environment (u-b
Dear Bharat Bhushan,
In message you
wrote:
>
> u-b>mtdparts
> device nor0 , # parts =3D 5
> #: namesizeoffset mask_flags
> 0: boot0x0004 0x 0
> 1: boot_config 0x0001 0x0004 0
> 2: bo
Hi,
I am currently working on AMCC Kilauea eval board. I am using u-boot 2009.3.
I boot my board from nand. By default, when booting from nand, the environment
(u-boot parameters) are embedded to u-boot. I am interested to know if it is
possible to get u-boot environment parameters out of u
Hi Detlev,
On Tue, May 12, 2009 at 9:10 PM, Detlev Zundel wrote:
> Hi Bharat,
>
> [re-adding the mailing list as others may also profit from the
> discussion]
>
> > Thank you for the prompt reply.
> >
> > Unfortunately in linux tree, my board specific MTD partition info is not
> > preset.
> >
>
Interesting. I've tried to use your patch but still hanging board_init_f.
Even putting BOOKE_PAGESZ_256M in set_tlb the problem occur.
On Thu, May 14, 2009 at 2:49 PM, Fredrik Arnerup <
fredrik.arne...@edgeware.tv> wrote:
> > The tlb settings looks fine (debbug in setup_ddr_tlbs()):
> >
> > ram_t
On May 14, 2009, at 12:38 PM, Fredrik Arnerup wrote:
> The MAXSIZE field in the TLB1CFG register is 4 bits, not 8 bits.
> This made setup_ddr_tlbs() try to set up a TLB larger than the e500
> maximum
> (256 MB)
> which made u-boot hang in board_init_f() when trying to create a new
> stack
> i
Hi Alfred,
alfred steele wrote:
> Hi Ilya,
>
>>/* Now try to get the SD card's operating condition */
>>err = sd_send_op_cond(mmc);
>>
>
> I am using your set of patches on the MX31 board. I am not getting any
> command response for the sd_send_op_cond(mmc) called from the
> The tlb settings looks fine (debbug in setup_ddr_tlbs()):
>
> ram_tlb_address: 0x0, ram_tlb_address: 0x0, ram_tlb_index: 0x8, tlb_size:
0xa
> ram_tlb_address: 0x4000, ram_tlb_address: 0x4000, ram_tlb_index:
0x9, tlb_size: 0xa
"tlb_size: 0xa" is _not_ fine.
Quoting the 8540 reference man
The MAXSIZE field in the TLB1CFG register is 4 bits, not 8 bits.
This made setup_ddr_tlbs() try to set up a TLB larger than the e500 maximum
(256 MB)
which made u-boot hang in board_init_f() when trying to create a new stack
in RAM.
I have an mpc8540 with one 1GB dimm.
Signed-off-by: Fredrik Arner
Hello,
my mpc8572ds (2x 512 MiB ram) had initially u-boot 1.3.0-rc2 and I
haven't notice any problems. Today I updated u-boot to v2009.03 because
I was not able to boot current vanilla linux kernel in smp mode.
Since then I experience random kernel opses. I thing it has something to
do with memory
Hi,
I'm working on a mpc85xx board very similar to MPC8548CDS. I have 2 DIMMs
and each one with it own spd eeprom and with only one chip select (cs0 and
cs2). I'm trying to use two 1Gb DDR2s. My ddr configurations:
/* DDR Setup */
#define CONFIG_VERY_BIG_RAM
#define CONFIG_FSL_DDR2
#undef CONFIG_
> My value was at 100. Switching back to 1000 didn't solve my problem,
> but instead causes erase and write operations on nand flash to timeout
> as well. My u-boot was built on commit
> 03bab0091948196b9558248684c04f60943ca4b5 of the at-91 tree.
this revision does not integrate the time
On Thursday 14 May 2009 17:01:46 Wolfgang Denk wrote:
> > > If this should be the highest level in the call chain, then any
> > > conditional calling should be done here.
> >
> > OK, I can move the conditional calling to this level.
>
> I'm not sure.
>
> > > But - don't we already have
> > >
Jean-Christophe PLAGNIOL-VILLARD schrieb:
On 13:37 Wed 13 May , Achim Ehrlich wrote:
Jens Gehrlein schrieb:
Wolfgang Denk schrieb:
Dear Achim Ehrlich,
In message <4a0969fc.2060...@taskit.de> you wrote:
The timeout for lost packages in tftp.c is defined to 5000 msecs. But
when setting the
On Thursday 14 May 2009 16:59:51 Wolfgang Denk wrote:
> > > If my understanding is correct, then this is a bug on your hardware.
> >
> > I don't think so.
>
> I do, because what we see on other hardware looks different:
>
> For example:
>
> U-Boot 1.3.2-rc2-g02e4b4e3 (Feb 28 2008 - 16:46:26)
Dear Stefan Roese,
In message <200905141613.20127...@denx.de> you wrote:
>
> > If this should be the highest level in the call chain, then any
> > conditional calling should be done here.
>
> OK, I can move the conditional calling to this level.
I'm not sure.
> > But - don't we already h
Dear Stefan Roese,
In message <200905141555.33901...@denx.de> you wrote:
>
> > > IDE: Bus 0: OK Bus 1: OK
> > > Device 0: Model: HITACHI_DK23FA-20J Firm: 00M7A0A0 Ser#: 42D182
> > > Type: Hard Disk
> > > Capacity: 19077.1 MB = 18.6 GB (39070080 x 512)
> > > Device 1:
Hi Ilya,
> /* Now try to get the SD card's operating condition */
> err = sd_send_op_cond(mmc);
I am using your set of patches on the MX31 board. I am not getting any
command response for the sd_send_op_cond(mmc) called from the mmc. I
think you claimed it will work on mxcs includi
Dear all,
I am new with U-Boot, and I am trying to access the content of a JFFS2
partition from u-boot.
I am working with an at91sam9263 board, with nand flash.
In u-boot, I added the #define CONFIG_CMD_JFFS2, as well as
CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE and CONFIG_JFFS2_NAND_DEV.
I
On Thursday 14 May 2009 16:02:00 Wolfgang Denk wrote:
> > Then please let me know how this can be accomplished. The CPCI750 uses
> > the same U-Boot image both for the video-enabled CPCI-host version and
> > for the video-disabled CPCI-adapter version. The video driver is not
> > called from within
Dear Stefan Roese,
In message <200905141553.20682...@denx.de> you wrote:
>
> I would love to do it this way. It's not possible though. At least I don't
> see
> such a solution.
Of course it's possible. Anything is possible in software :-)
> Then please let me know how this can be accomplished.
Dear Sascha,
in message <20090514134055.ga29...@pengutronix.de> you wrote:
>
> > It is incorrect to state that "Linux uses offsets for registers". The
> > Linux code for ARM may do this, and I consider this one of the major
> > deficiencies of the ARM code in Linux. Other architectures (like
> > P
Hi Wolfgang,
On Thursday 14 May 2009 15:44:01 Wolfgang Denk wrote:
> > Currently only IDE busses are probed and all possible available devices
> > are listed in the IDE bootup log. Even when devices on the bus are not
> > available. This leads to the following output on the CPCI750:
> >
> > IDE:
Hi Wolfgang,
On Thursday 14 May 2009 15:37:15 Wolfgang Denk wrote:
> > This patch adds an option to skip the video initialization on the
> > ct6900. This is needed for the CPCI750 which can be built as CPCI
> > host and adapter/target board. And the adapter board can't access the
> > video cards.
Dear Stefan Roese,
In message <1242278687-23685-1-git-send-email...@denx.de> you wrote:
> Currently only IDE busses are probed and all possible available devices
> are listed in the IDE bootup log. Even when devices on the bus are not
> available. This leads to the following output on the CPCI750:
On Thu, May 14, 2009 at 10:10:07AM +0200, Wolfgang Denk wrote:
> Dear Ilya Yanok,
>
> In message <4a0b4f9a.8030...@emcraft.com> you wrote:
> >
> > >> +return 2600 / 1.5;
> > >
> > > We definitely do not allow any FP use in U-Boot.
> >
> > This will be actually converted to an
Dear Stefan Roese,
In message <1242278732-23803-1-git-send-email...@denx.de> you wrote:
> This patch adds an option to skip the video initialization on the
> ct6900. This is needed for the CPCI750 which can be built as CPCI
> host and adapter/target board. And the adapter board can't access the
>
Dear Ilya,
In message <4a0bf1cf.9030...@emcraft.com> you wrote:
>
> Another issue I've just faced: how we are going to access IO registers
> from assembler code? I don't think we have that asm-offsets stuff in
> U-Boot...
I faced the same problem with the recent MPC512x patches; I think
it's
Dear Wolfgang,
Wolfgang Denk wrote:
>> I see. PowerPC in Linux uses C structs too. But there are still a lot of
>> code that uses registers offsets in Linux, so my arguments are the same:
>> requirement to convert offsets to C struct brings additional
>> difficulties to porting (and maintaining al
Return value of mmc_send_if_cond() can be safely ignored (as it is
done in Linux). This makes older cards work with MXC MCI controller.
Signed-off-by: Ilya Yanok
---
drivers/mmc/mmc.c |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/drivers/mmc/mmc.c b/drivers/mmc/mmc.
On Wednesday 13 May 2009 10:56:00 Kazuaki Ichinohe wrote:
> This patch adds a SATA harddisk driver for the canyonlands.
> This patch is kernel driver's porting.
> This pach corresponded to not cmd_scsi but cmd_sata.
>
> [environment variable, boot script]
> setenv bootargs root=/dev/sda7 rw
> seten
Dear Ilya,
in message <4a0be30f.9070...@emcraft.com> you wrote:
>
> Well, out_be32() and friends don't convert pointer, you are right. But
> these functions are not really generic, they can be found only on couple
> of archs. And writel() and friends (which are generic accessor functions
> for MMI
Hi Wolfgang,
Wolfgang Denk wrote:
>> Ok, I really like using accessor calls instead of pointer accesses but I
>> don't really understand the reason for using C structs here... I
>> remember I've already asked you about that and you told me that it's for
>> type safety... But we loose this type-saf
On Thursday 14 May 2009 10:28:08 Kazuaki Ichinohe wrote:
> I sent the patch source again on May 13.
> Could you review the patch source again ?
Yes, will do.
Best regards,
Stefan
=
DENX Software Engineering GmbH, MD: Wolfgan
The folowing patch tries to fix all defects of the previous patch.
The new led command is _not_ limited to 3 LEDs any more, but it
is still restricted to at91 architectures.
Best regards,
Daniel Gorsulowski
___
U-Boot mailing list
U-Boot@lists.denx.de
ht
This patch allows any at91 board implementing the GPIO LED API
to control vendor specific LEDs from the console.
Adding configuration items CONFIG_AT91_LED and CONFIG_CMD_LED
enables the command.
Moreover the GPIO Pins have to be defined by CONFIG_GPIO_LEDS
See doc/README.LED for detailed informat
>> BTW, I know u-boot can pass the mtdparts parameters to linux kernel.
>> Which mtd partition info linux kernel will use, u-boot mtdparts info
>> or static address map code ?
>
> That's a Linux question, isn't it? And as such off topic here...
>
> The answer is: it depends.
>
> If you don't config
Hello Denk, Stefan,
I sent the patch source again on May 13.
Could you review the patch source again ?
Regards,
Kazuaki Ichinohe
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Dear "H. Johnny",
In message <50a974c70905132045t73c26b97i9a245219e60fd...@mail.gmail.com> you
wrote:
>
> BTW, I know u-boot can pass the mtdparts parameters to linux kernel.
> Which mtd partition info linux kernel will use, u-boot mtdparts info
> or static address map code ?
That's a Linux ques
Dear Ilya Yanok,
In message <4a0b4f9a.8030...@emcraft.com> you wrote:
>
> >> + return 2600 / 1.5;
> >
> > We definitely do not allow any FP use in U-Boot.
>
> This will be actually converted to an integer at the compile time.
Maybe. But it's also trivial not to use any FP calculati
Hi All,
I have a custom board similar to MPC8560ADS board with 1GB DDR SDRAM. The DDR
SDRAM Make
is MT18VDDF12872DG-335D3. In U-BOOT (2009.01) config file I have enabled
CONFIG_SPD_EEPROM
so U-boot configures MPC8560ADS DDR controller with the values read from
SPD_EEPROM (i2c
address 0x51)
Af
70 matches
Mail list logo