All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Damborsky <jan.damborsky@devcom.cz>
To: Wolfgang Denk <wd@denx.de>, linuxppc-dev@lists.linuxppc.org
Subject: Re: MPC823E SMC/I2C/SPI micropatch
Date: Mon, 26 Jan 2004 10:25:49 +0100	[thread overview]
Message-ID: <4014DD1D.8070704@devcom.cz> (raw)
In-Reply-To: <20040126080100.26782C108D@atlas.denx.de>


I think I have selected the __correct__ one.
Situated in ./arch/ppc/8xx_io/micropatch_850.c file.
- relocates I2C, SPI, SMC parameter RAM.
- it is determined for 850 and 823E processors (I hope).
- I had to define USE_SMC_PATCH and write some
   additional code for relocating SMC parameter RWM
   in cpm_load_patch() function (./arch/ppc/8xx_io/micropatch.c)
   as well as in SMC UART code (./arch/ppc/8xx_io/uart.c).
More additional hacks needed:
* original RPBASE set to 0x400 clashed with SMC micropatch
   so I redefined it to 0x800
* when used ethernets on SCC2,SCC3 with CONFIG_ENET_BIG_BUFFERS
   enabled, they need 2kB of DPRAM - it cannot fit together with
   micropatch in first 4kB of DPRAM, so I redefined
   CPM_DATAONLY_BASE to 0x1000 and CPM_DATAONLY_SIZE to 0x0c00

And for now, I have SCC2,SCC3 ethernets
and SMC1,SMC2 UARTs working altogether.

                               Sincerely, Jan Damborsky

Wolfgang Denk wrote:
> In message <4014C088.1020208@devcom.cz> you wrote:
>
>>I have found out that CPM micropatch
>>available in linux-2.4 from Wolfgang Denk
>>site (the kernel we use successfuly on our
>>custom boards at present) is applicable as well.
>
>
> You have to select the _correct_ uCode patch.
>
> There is one patch for the MPC850, and another one for all other  8xx
> processors. And there is the USB SOF potch for the MPC823.
>
>
> Best regards,
>
> Wolfgang Denk
>
> --
> See us @ Embedded World, Nuremberg, Feb 17 - 19,  Hall 12.0 Booth 440
> Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
> Another dream that failed.  There's nothing sadder.
> 	-- Kirk, "This side of Paradise", stardate 3417.3
>
>
>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-01-26  9:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 16:29 MPC823E SMC/I2C/SPI micropatch Steven Blakeslee
2004-01-19 16:44 ` Jan Damborsky
2004-01-26  7:23 ` Jan Damborsky
2004-01-26  8:00   ` Wolfgang Denk
2004-01-26  9:25     ` Jan Damborsky [this message]
2004-01-26  9:33       ` Wolfgang Denk
2004-01-26 10:29         ` Jan Damborsky
2004-01-26 11:31           ` Wolfgang Denk
2004-01-26 11:52             ` Jan Damborsky
  -- strict thread matches above, loose matches on Subject: below --
2004-01-19 16:20 Jan Damborsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4014DD1D.8070704@devcom.cz \
    --to=jan.damborsky@devcom.cz \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=wd@denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.