Hi Matt
This might be a very basic question. By porting what do you mean?. As of now
I copied the ebony bsp to different location and did changes to boot on the
custom board. Till now it was booting without any problem. Once I changed
the EBC configuration to configure some other FPGA ,bcos of wh
Ing.Gianfranco Morandi wrote:
> I have promised to Pete of releasing some code for such driver. We will
> provide to perform such task during the next days.
Thank you very much for this information. Since I will be working on
that, I will also be glad to contribute something to your activities.
>
On 12/13/2002 05:07 PM Steve Rossi wrote:
> I've seen some reference on the list regarding a driver for the 823
> Video Controller -
> i.e.
> http://lists.linuxppc.org/results.html?restrict=linuxppc-embedded&words=vid823
> however I've been unable to locate the source to vid823.c
> apparently this
Dear Steve,
in message <3DFA05C3.30703 at ccrl.mot.com> you wrote:
>
> I've seen some reference on the list regarding a driver for the 823
> Video Controller -
> i.e.
> http://lists.linuxppc.org/results.html?restrict=linuxppc-embedded&words=vid823
> however I've been unable to locate the source t
I mean that by using the revision A.1 You could have some troubles.
Main reason is related to the Global Underrun (GUN) that often occours when
many channels are active (we use continuosly 64 channels on one mcc). This
issue has been repored by Motorola in its document "mpc8260cesumm.pdf" and
fina
Hi folks,
Does anyone out there work on 440 based PCI board?
I have a DMA problem with the 440 DMA controller. In
our application, the 440 based PCI board is living in
a Solaris host platform. Our PCI board is running with
linux version 2.4.17. So, there are Host software,
driver and embedded li
The patch below adds support for IBM's Arctic-II development system,
based on the 405LP processor. For now this is just the core support,
more drivers coming soon. Are there any objections, or suggestions
for doing things better before I commit this to linuxppc_2_4_devel?
In particular, I'd wel
hi.
we made custom board(cpu is MPC8245)
kernel is 2.4.18
our application sometimes stop with the message "Segmentation fault"or
"illegal instruction".
So i searched this message on kernel source code by grep command.
But i could not find this message "Segmentation fault".
somebody tell me where i
A few comments and questions...
I assume symbol CONFIG_ARCTIC2 is more appropriate than CONFIG_ARCTIC,
with additional symbols possibly to be invented in the future to
distinguish minor changes in board rev 3, 4, ... But mentioning this
just in case it might make future maintenance easier to use
Hi,
Anybody succeeded in compiling ucd-snmp.4.2.6 using ELDK? Could you
please share
your option run with configure?
I have compiled one, but only can snmpget/snmpwalk/etc, but can not
snmpset, it always
returns timeout.
Thanks
Jin
** Sent via the linuxppc-embedded mail list. See http://lists
I have promised to Pete of releasing some code for such driver. We will
provide to perform such task during the next days.
Actually we are writing some documents to better describe the driver and how
to lock it to the kernel tree.
We will inform the community when the driver will be available.
A
On Fri, Dec 13, 2002 at 09:35:22PM +0530, Aman wrote:
> This might be a very basic question. By porting what do you mean?. As of now
By "porting", I mean adding a set of code that reflect the unique
characteristics of your custom board.
> I copied the ebony bsp to different location and did chan
On Thu, Dec 12, 2002 at 10:17:44AM -0600, Hollis Blanchard wrote:
> On Wed, 2002-12-11 at 21:54, David Gibson wrote:
> >
> > The RTC support (written by Todd Poynor) for the Beech is actually in
> > the 405LP chip itself, not just on the Beech board.
>
>
> As a separate patch (either before or af
I've seen some reference on the list regarding a driver for the 823
Video Controller -
i.e.
http://lists.linuxppc.org/results.html?restrict=linuxppc-embedded&words=vid823
however I've been unable to locate the source to vid823.c
apparently this question was asked before:
http://lists.linuxppc.org/
On Fri, Dec 13, 2002 at 08:16:43AM -0700, Tom Rini wrote:
[snip]
> If you aren't already on the linuxppc-commit at source.mvista.com list, you
> might want to join that.
And since this is at a possibly non obvious location:
http://source.mvista.com/cgi-bin/mailman/listinfo/linuxppc-commit
Hopef
On Fri, Dec 13, 2002 at 08:18:08AM -0700, Tom Rini wrote:
>
> On Thu, Dec 12, 2002 at 09:51:26PM -0700, Cort Dougan wrote:
>
> > Would you be able to commit them to _2_4 instead so they're not in the
> > wildly divergent _2_4_devel tree? That would definitely be handy when
> > trying to find wher
On Thu, Dec 12, 2002 at 09:51:26PM -0700, Cort Dougan wrote:
> Would you be able to commit them to _2_4 instead so they're not in the
> wildly divergent _2_4_devel tree? That would definitely be handy when
> trying to find where the working trees are.
One of my goals for winter break is to try
On Fri, Dec 13, 2002 at 07:26:02AM -0700, Gary Thomas wrote:
> On Thu, 2002-12-12 at 21:51, Cort Dougan wrote:
> >
> > Would you be able to commit them to _2_4 instead so they're not in the
> > wildly divergent _2_4_devel tree? That would definitely be handy when
> > trying to find where the wor
On Thu, 2002-12-12 at 21:51, Cort Dougan wrote:
>
> Would you be able to commit them to _2_4 instead so they're not in the
> wildly divergent _2_4_devel tree? That would definitely be handy when
> trying to find where the working trees are.
>
> } The patch below adds support for IBM's Arctic-II d
> Be aware do not use the mcc with the silicon revision older than B.1.
Could you provide more information on this comment. There are lots of
reasons not to use a rev A.1 chip. This is the first time that I heard about
using too new of a chip.
THX
** Sent via the linuxppc-embedded mail list. S
20 matches
Mail list logo