All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Masters <jonmasters@gmail.com>
To: Andrei Konovalov <akonovalov@ru.mvista.com>
Cc: akpm@osdl.org, linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH][PPC32] Xilinx ML300 board support (very basic)
Date: Sat, 9 Oct 2004 20:40:31 +0100	[thread overview]
Message-ID: <35fb2e5904100912409628a94@mail.gmail.com> (raw)
In-Reply-To: <4166CCF5.7040705@ru.mvista.com>

On Fri, 08 Oct 2004 21:23:01 +0400, Andrei Konovalov
<akonovalov@ru.mvista.com> wrote:

> Adds minimal Xilinx ML300 board support (enough to boot with ramdisk).
> The only peripheral devices supported are 16x50 compatible UARTs.
> 
> Signed-off-by: Andrei Konovalov <akonovalov@ru.mvista.com>

I'll test this if I get chance soon.

>         /*
> -        * At one point, we were getting machine checks.  Linux was not
> -        * invalidating the data cache before it was enabled.  The
> -        * following code was added to do that.  Soon after we had done
> -        * that, we found the real reasons for the machine checks.  I've
> -        * run the kernel a few times with the following code
> -        * temporarily removed without any apparent problems.  However,
> -        * I objdump'ed the kernel and boot code and found out that
> -        * there were no other dccci's anywhere, so I put the code back
> -        * in and have been reluctant to remove it.  It seems safer to
> -        * just leave it here.
> +        * Invalidate the data cache if the data cache is turned off.
> +        * - The 405 core does not invalidate the data cache on power-up
> +        *   or reset but does turn off the data cache. We cannot assume
> +        *   that the cache contents are valid.
> +        * - If the data cache is turned on this must have been done by
> +        *   a bootloader and we assume that the cache contents are
> +        *   valid.
>          */

Er...the caveat about the MSR is still worth noting - I had this
problem and for a while couldn't figure out why the fsck the board
wouldn't come up with cacheing enabled (I've written patches for
debugging that turn off various cacheing by modifying the pte macros,
etc.) and *still* believe we're not clean from unwanted machine checks
here. Just FYI.

> +/* We don't need anything mapped.  Size of zero will accomplish that. */
> +#define PPC4xx_ONB_IO_PADDR    0u
> +#define PPC4xx_ONB_IO_VADDR    0u
> +#define PPC4xx_ONB_IO_SIZE     0u

:-)

> +*     This program is free software; you can redistribute it and/or modify it
> +*     under the terms of the GNU General Public License as published by the
> +*     Free Software Foundation; either version 2 of the License, or (at your
> +*     option) any later version.

...and then:

> +*     Xilinx hardware products are not intended for use in life support
> +*     appliances, devices, or systems. Use in such applications is
> +*     expressly prohibited.

I've always loved it how Xilinx GPL disclaimers cunningly aren't. They
might want to wake up and smell the coffee at some point.

Andrei, you'll want to modify the ML300 xparameters stuff to allow
it's location to be specified by a parameter. People who want to use
(ewww, spit) autogenerated Xilinx xparameters.h from their EDK will
probably also want to choose where it lives.

> + * arch/ppc/syslib/xilinx_pic.c
> + *
> + * Interrupt controller driver for Xilinx Virtex-II Pro.

Nice. Better than the original and now handles different types of interrupts.

Jon.

  reply	other threads:[~2004-10-09 19:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 17:23 [PATCH][PPC32] Xilinx ML300 board support (very basic) Andrei Konovalov
2004-10-09 19:40 ` Jon Masters [this message]
2004-10-11 11:53   ` Andrei Konovalov
2004-10-11 12:23     ` Jon Masters
2004-10-11 15:19   ` Tom Rini
2004-10-11 16:23     ` Jon Masters

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=35fb2e5904100912409628a94@mail.gmail.com \
    --to=jonmasters@gmail.com \
    --cc=akonovalov@ru.mvista.com \
    --cc=akpm@osdl.org \
    --cc=jonathan@jonmasters.org \
    --cc=linuxppc-embedded@ozlabs.org \
    /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.