From: "Wade Maxfield" <wmaxfield@gmail.com>
To: "T Ziomek" <ctz001@email.mot.com>
Cc: ppc <linuxppc-embedded@ozlabs.org>
Subject: Re: MontaVista 2.6 Kernel support for Xilinx ML40x
Date: Thu, 24 Aug 2006 17:13:24 -0500 [thread overview]
Message-ID: <45a1b53e0608241513m5b97d34chf7e133eea984cb6c@mail.gmail.com> (raw)
In-Reply-To: <Pine.WNT.4.61.0608241432311.200@holyoke.labs.mot.com>
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
sorry! ;) See my reply at the right location!
On 8/24/06, T Ziomek <ctz001@email.mot.com> wrote:
>
> [top-posting fixed :-) ]
>
>
> On Thu, 24 Aug 2006, Wade Maxfield wrote:
> >
> > On 8/24/06, Peter Ryser <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.
> >
> > 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.
>
> When we were using the eval version of Xilinx's 10/100 EMAC it would time-
> out after 8 hours (and the kernel would panic since our root fs was NFS-
> mounted).
>
> If your only [to-be-]licensed core is Ethernet, then I take it you're
> using
> the UARTLite, or a non-Xilinx UART? We used Xilinx's 16550-compatible
> UART,
> which is licensed, but I never ran with the eval version of that IP block
> and so have no idea how long it will function before shutting down.
We are doing an evaluation right now. We have operational 8 hours 55
minutes so far and counting on the Xilinx 16550 compatible uart. I think
that is the cause of the problem for us, but not sure so far.
Tom
> --
> A: Because it breaks the logical |
> flow of the message. | Email to user 'CTZ001'
> | at 'email.mot.com'
> Q: Why is top posting frowned upon? |
x<>y
A2. but only for algebraic. RPN likes it that way.
[-- Attachment #2: Type: text/html, Size: 2928 bytes --]
next prev parent reply other threads:[~2006-08-24 22:13 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
2006-08-24 19:38 ` T Ziomek
2006-08-24 22:13 ` Wade Maxfield [this message]
-- 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=45a1b53e0608241513m5b97d34chf7e133eea984cb6c@mail.gmail.com \
--to=wmaxfield@gmail.com \
--cc=ctz001@email.mot.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).