Hi Matthias,
Stefan Roese schrieb:
> Hi Matthias,
>
> On Wednesday 27 October 2010 08:55:42 Matthias Dunda wrote:
>> unfortunately I have to push this message, as I received no comment on it,
>> yet.
>>
>> Is there a reason why the immap_t is not implemented for mpc85xx?
>>
>> I tried to copy it
Hi André,
André Schwarz schrieb:
> I'm running on MVBLM7 board using CONFIG_SYS_HUSH_PARSER.
>
> While working on some scripts using env-variables holding some physical
> address values I stumbled over this :
>
>
> my env-variables used :
>
> loadaddr=0x40
> kernel_addr=0xff81000
> kernel_
Hi Kumar,
Kumar Gala schrieb:
> On Oct 27, 2009, at 10:29 AM, Luigi 'Comio' Mantellini wrote:
>
>> Hi All,
>>
>> I'm working on a stripped-down mpc8541 board (that has just
>> a serian and twe enets).
>> I have an issue on delay calibration. In fact at boot time, I see the
>> following linux prin
Hi Alemao,
Alemao schrieb:
> Hi all,
>
> I have used UPM in a MPC83xx with LBC running at 64MHz.
>
> Now I have a MPC85xx, with LBC at 41MHz.
>
> It only works if I put a delay in drivers/mtd/nand/fsl_upm.c :
> nand_write_buf(), otherwise I lost one byte. But it takes t long
> writing, whic
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 timeout get_timer(0) is called in NetSetTimeout in net.c.
>> But on AT91 the timer code returns usecs an
Peter Tyser schrieb:
> You should be able to use the 85xx DMA engine to generate the bursts too
> (I'd assume the same for 83xx, but never tried it). See
> cpu/mpc85xx/cpu.c dma_*(). The default values of the satr0 and datr0
> don't allow the processor to snoop transactions, so you'd have to use
Dear Wolfgang Denk,
Wolfgang Denk schrieb:
> Dear Jens Gehrlein,
>
> In message <49d323e5.9080...@tqs.de> you wrote:
>> AFAIK, while running from flash, u-boot uses (part of) d-cache on some
>> platforms for the C stack. I think, it's on MPC83xx and MPC85xx?
>&
Liu Dave-R63238 schrieb:
>>> AFAIK, while running from flash, u-boot uses (part of)
>> d-cache on some
>>> platforms for the C stack. I think, it's on MPC83xx and MPC85xx?
>>>
>>> Does anybody know, if I can use the remaining part of the d-cache
>>> as normal d-cache, e.g. to generate bursts on th
Hi,
AFAIK, while running from flash, u-boot uses (part of) d-cache on some
platforms for the C stack. I think, it's on MPC83xx and MPC85xx?
Does anybody know, if I can use the remaining part of the d-cache
as normal d-cache, e.g. to generate bursts on the SDRAM interface
while testing the RAM?
K
Hi,
currently drivers/video/mx3fb.c contains some defines, which are
usually board specific:
#define XRES240
#define YRES320
#define PANEL_TYPE IPU_PANEL_TFT
#define PIXEL_CLK 185925
#define PIXEL_FMT IPU_PIX_FMT_RGB666
#define H_START_WIDTH 9
Hi Andy,
Andy Fleming schrieb:
> The ecm variable in sdram.c was being declared for all 8548, but only
> used by specific 8548 boards, so we make that variable require those
> specific boards, too
>
[snip]
> diff --git a/board/tqc/tqm85xx/sdram.c b/board/tqc/tqm85xx/sdram.c
> index 2b3de44..6d7
hendrik schrieb:
> Thank you Jens, I found "MPC8458ECE Rev. 2" but can not find a page 2 or
> errata considering CPU 1.1 to 2.1 is there another link to the document?
Within this document, a very lengthy table 3, starting at page 2,
describes (hopefully ;-) ) all known errata. On the right side
Hi hendrik,
hendrik schrieb:
> Hi all
>
> could someone pls point me to where i can find documentation regarding
> changes and the implications there of between die Freescale mpc8548 v1
> and v2 silicone CPUs. I have searched Freescales website but only turned
> up errata concerning the refere
Hi Stefan,
Stefan Roese schrieb:
> On Tuesday 16 December 2008, Jens Gehrlein wrote:
>> The following patches should increase the performance of the CFI driver,
>> particularly with regard to single word programming mode.
>>
>> I tested it on TQM5200S with NOR-Flash Sa
Jean-Christophe PLAGNIOL-VILLARD schrieb:
> diff --git a/board/imx31_phycore/imx31_phycore.c
> b/board/imx31_phycore/imx31_phycore.c
> index ae93444..4b72d57 100644
> --- a/board/imx31_phycore/imx31_phycore.c
> +++ b/board/imx31_phycore/imx31_phycore.c
> @@ -60,7 +60,7 @@ int board_init (void)
>
Dear Jean-Christophe,
Jean-Christophe PLAGNIOL-VILLARD schrieb:
> On 17:46 Tue 16 Dec , Jens Gehrlein wrote:
>> Jean-Christophe PLAGNIOL-VILLARD schrieb:
>>> On 17:25 Tue 16 Dec , Jens Gehrlein wrote:
>>>> Hi list,
>>>>
>>>> The follow
Jean-Christophe PLAGNIOL-VILLARD schrieb:
> On 17:25 Tue 16 Dec , Jens Gehrlein wrote:
>> Hi list,
>>
>> The following patches should increase the performance of the CFI driver,
>> particularly with regard to single word programming mode.
>>
>> I teste
Tested on TQM5200S-BD with Samsung K8P2815UQB
Signed-off-by: Jens Gehrlein
---
drivers/mtd/cfi_flash.c | 23 ---
1 files changed, 16 insertions(+), 7 deletions(-)
diff --git a/drivers/mtd/cfi_flash.c b/drivers/mtd/cfi_flash.c
index 1bd0e2b..bc5e151 100644
--- a/drivers
The function find_sector() doesn't need to be called twice in
the case of AMD command set.
Tested on TQM5200S-BD with Samsung K8P2815UQB.
Signed-off-by: Jens Gehrlein
---
drivers/mtd/cfi_flash.c | 10 +++---
1 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/driver
other HW, particularly top boot, other CPU, other flash
width, please?
Thanks,
Jens
---
Jens Gehrlein (2):
CFI: increase performance of function find_sector()
CFI: avoid redundant function call in single word programming mode
drivers/mtd/cfi_flash.c
Hi Scott,
Scott Wood schrieb:
> On Mon, Dec 15, 2008 at 08:26:03AM +0100, Jens Gehrlein wrote:
>> Hi Ron,
>>
>> Ron Madrid schrieb:
>>> Currently there are in excess of 100 bytes located at the beginning of the
>>> image
>>> built by start.S th
Hi Ron,
Ron Madrid schrieb:
> Currently there are in excess of 100 bytes located at the beginning of the
> image
> built by start.S that are not being utilized.
Hmmm, are you sure? What if someone designs a board, where the processor
shall load its reset configuration from a local bus EEPROM, e.
Hi Wolfgang,
Wolfgang Denk schrieb:
> Dear Jens Gehrlein,
>
> In message <490edd63.1010...@tqs.de> you wrote:
>> find_sector() loops through the sector table from the last sector to
>> the current sector. And the more sectors the device has, the slower
>> the al
Hi list,
having a look at function
drivers/mtd/cfi_flash.c::flash_write_cfiword(), I found that
find_sector() is called twice when having AMD standard, extended or
legacy device. The first time, when writing the command. The second
time, when calling flash_full_status_check().
Maybe this is t
Wolfgang Denk schrieb:
> Hi everybody,
>
> here some custodian news:
>
> 1) Kyungmin Park is now custodian for the (new) "u-boot-ubi" reposi-
>tory where UBI related work will be added. Thanks to Kyungmin Park
>for volunteering.
>
> 2) Anatolij Gustschin is now custodian for the "u-boot
Hi Jason,
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Jason Jin
> Sent: Friday, September 19, 2008 11:33 AM
> To: [EMAIL PROTECTED]
> Cc: u-boot@lists.denx.de; Jason Jin
> Subject: [U-Boot] [PATCH 1/4] Fix the NAND size overflow issue.
>
>
> When
Hi Wolfgang, hi Andrew,
> Please restrict your line length to something readable, i. e. some 70
> characters or so. Thanks.
OK. It seems Outlo*k needs some manual override...
Hope, this mail is better...
> > Is it intended, that the watchdog isn't triggered in
> U-Boot's interactive mode? I can
Hi,
I initialized the watchdog on a S3C6400 processor. The U-Boot boots fine until
the command line prompt.
If I don't use the hush parser, watchdog resets the board approx. after 15
seconds, no matter if I do nothing or if I type in commands.
Reading the watchdog counter with "md" shows that i
ect ARM Versatile Timer Initialization
>>
>> Hugo Villeneuve (2):
>> ARM DaVinci: Fix compilation error with new MTD code.
>> ARM DaVinci: Removed redundant NAND initialization code.
>>
>> Jens Gehrlein (1):
>> MX31: fix bit masks in functi
Scott Wood schrieb:
> On Wed, Aug 13, 2008 at 07:03:25PM +0200, Jens Gehrlein wrote:
>> Hi,
>> in nand_spl/nand_boot.c in function nand_read_page() one can read the
>> comment in the case of ECC errors:
>> "No chance to do something with the possible error message
Hi,
in nand_spl/nand_boot.c in function nand_read_page() one can read the
comment in the case of ECC errors:
"No chance to do something with the possible error message from
correct_data(). We just hope that all possible errors are corrected by
this routine."
Why can't we do anything? If an unc
Hi,
in the directory nand_spl/board one can find three subdirectories: amcc,
freescale and samsung, which contain the reference boards of these
vendors. These vendors are CPU vendors, too.
When I want to add a new board, shall I create a board's vendor
directory directly in nand_spl/board, or
32 matches
Mail list logo