All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank D Lombardo <lombardo@mdivac.com>
To: Wade Maxfield <wmaxfield@gmail.com>
Cc: ppc <linuxppc-embedded@ozlabs.org>
Subject: Re: MontaVista 2.6 Kernel support for Xilinx ML40x
Date: Thu, 24 Aug 2006 15:27:24 -0400	[thread overview]
Message-ID: <44EDFD9C.4010003@mdivac.com> (raw)
In-Reply-To: <45a1b53e0608241057j4ebe519drd1e431a2275ccdde@mail.gmail.com>

The ml403 reference design has several evaluation cores: opb_uart16550, 
opb_iic and opb_ethernet.  They seem to time-out after about eight hours.

Frank

Wade Maxfield wrote:
> Good question.  How long before lockup?  The only core that should be 
> licensed is the ethernet, and I know it was sysgened on a system with 
> a license.  This is the Xilinx reference design for the ml403 board.
>
>
> On 8/24/06, *Peter Ryser* <peter.ryser@xilinx.com 
> <mailto:peter.ryser@xilinx.com>> wrote:
>
>     Wade,
>
>     are you sure that you did not build your hardware with evaluation
>     cores of the licenses? If you are using the evaluation licenses
>     the hardware (FPGA design) will stop working after a certain
>     amount of time and you will see a lock-up.
>
>     - Peter
>
>
>     Wade Maxfield wrote:
>
>       I've got the LSP, and have booted it on the ML40X.
>      
>       In my opinion it is currently unstable, but that is my opinion. 
>     I've not been able to keep it powered up for 24 hours without it
>     locking up on the RS232 serial terminal.  Also, running updatedb
>     over nfs causes it to abort with a kernel panic, although that
>     might be an interraction with the nfs server.  (Although even if
>     the nfs server dies (which it did not), I don't expect a kernel
>     panic).
>
>        I have had it run over 6 hours without issue, so I expect
>     subtle memory leaks, not serious problems.
>
>
>
>     On 8/24/06, *Claus Gindhart* < claus.gindhart@kontron.com
>     <mailto:claus.gindhart@kontron.com>> wrote:
>
>         Frank,
>
>         due to my understanding of the GPL (and i have already
>         invested some time
>         in understanding the various flavours of open source
>         licences), you should
>         contact Montavista, and ask them for the sources.
>
>         This board adaption is derivative work of the GPL Kernel, so
>         the result of
>         this work also falls under the GPL, and has to be made freely
>         available
>         under the terms of the GPL.
>
>         --
>         Mit freundlichen Gruessen / Best regards
>
>         Claus Gindhart
>         SW R&D
>         Kontron Modular Computers
>         phone :++49 (0)8341-803-374
>         mailto:claus.gindhart@kontron-modular.com
>         <mailto:claus.gindhart@kontron-modular.com>
>         http://www.kontron.com
>
>         -----BEGIN GEEK CODE BLOCK-----
>           Version: 3.1
>           GU d- s++:>++:+ a+ C++$ !U !P L++>$ E-- W+(-) N- o?
>           K? w !O !M V !PS PE- Y+ PGP+ t 5? X R* tv- b+ DI+++
>           D-- G e++> h--- !r x+++
>         ------END GEEK CODE BLOCK------
>
>
>         -----Original Message-----
>         From:
>         linuxppc-embedded-bounces+claus.gindhart=kontron.com@ozlabs.org
>         <mailto:kontron.com@ozlabs.org>
>         [mailto:
>         linuxppc-embedded-bounces+claus.gindhart=kontron.com@ozlabs.org
>         <mailto:linuxppc-embedded-bounces+claus.gindhart=kontron.com@ozlabs.org>]
>         On Behalf Of Frank D Lombardo
>         Sent: Donnerstag, 24. August 2006 15:59
>         To: linuxppc-embedded@ozlabs.org
>         <mailto:linuxppc-embedded@ozlabs.org>
>         Subject: MontaVista 2.6 Kernel support for Xilinx ML40x
>
>
>         I noticed that MontaVista now has their Pro 4.0 version (2.6
>         Kernel)
>         available for the Xilinx ML40x series of boards.  I would
>         assume that
>         means driver support for at least most of the hardware on the
>         boards.
>         Is this code that should be freely available?  How would one
>         get a copy
>         of these drivers?  I am interested in drivers for the ML403.
>
>         Thanks,
>         Frank
>         _______________________________________________
>         Linuxppc-embedded mailing list
>         Linuxppc-embedded@ozlabs.org <mailto:Linuxppc-embedded@ozlabs.org>
>         https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>         _______________________________________________
>         Linuxppc-embedded mailing list
>         Linuxppc-embedded@ozlabs.org <mailto:Linuxppc-embedded@ozlabs.org>
>         https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>         <https://ozlabs.org/mailman/listinfo/linuxppc-embedded>
>
>
>     ------------------------------------------------------------------------
>
>     _______________________________________________ Linuxppc-embedded
>     mailing list Linuxppc-embedded@ozlabs.org
>     <mailto:Linuxppc-embedded@ozlabs.org>
>     https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

  reply	other threads:[~2006-08-24 19:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24 15:02 MontaVista 2.6 Kernel support for Xilinx ML40x Claus Gindhart
2006-08-24 15:36 ` Wade Maxfield
2006-08-24 16:52   ` Peter Ryser
2006-08-24 17:57     ` Wade Maxfield
2006-08-24 19:27       ` Frank D Lombardo [this message]
2006-08-24 19:38       ` T Ziomek
2006-08-24 22:13         ` Wade Maxfield
  -- strict thread matches above, loose matches on Subject: below --
2006-08-24 15:40 Rick Moleres
2006-08-24 13:59 Frank D Lombardo
2006-08-24 15:17 ` Michael Galassi

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=44EDFD9C.4010003@mdivac.com \
    --to=lombardo@mdivac.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=wmaxfield@gmail.com \
    /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.