I'm using port D[0-3] (PD12-15) for data. FLM, CP and LP are coming from
PD[5,4,3]
It's a passive monochrome display. I've configured it as such. It should be
working.
(See Fig 18-4 in the book) It came with an 8 bit color NEC display that
worked, so I'm assuming there's a valid config already. I'
As you probably can guess I'm trying to get this Optrex display working.
Well I've finally scoped it out, and I can't find the cause (or solution to)
my problems.
When I write the following nibbles for display, I get these bit patterns out
of the pins and on screen:
0:
1: 1010
2: 0111
4: 010
.
dma_enable no longer clears mode bits. ( TODO: should document 4xx dma
usage)
Armin
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: dma_fix_0826.patch
Url:
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20020826/49578eae/att
hi,WD
> There are some more hints at
> http://www.denx.de/doc/TQM8xxL/debugging.html
I have read it before,but only for module or application,
not for kernel and ppcboot,someone told me because of
ppcboot's relocation,so it is difficult in some externd.
Anyway it helps some:)
> > I want to watch
In message <3D6A6D9D.20404 at redswitch.com> you wrote:
>
> > After running ppcboot on our board successfully (including the fast
> > ethernet LXT972), we have trouble on enabling FEC on linux kernel. The
> > problem is that we cannot send any packets through the network after the
> > kernel is bo
Shawn:
Maybe I have a contribution...
On Monday 26 August 2002 18:32, Xiaogeng (Shawn) Jin wrote:
> > You are passing bad/insufficient boot arguments to the Linux kernel;
> > unfortunaltely you don;t show us this part of the boot messages, so I
> > cannot even guess what you're doing wrong.
>
>
Have anybody experience with NFS root using PPP ?
I have ported 2.4.18 kernel to a factory developed 850 board.
It has two serial port but no ETH (the next version will have one).
How can I use the 2nd serial as NFS root dev?
Ludwig
** Sent via the linuxppc-embedded mail list. See http:
Hi,
in message <000901c24cfd$de617140$0141b73d at leeyang> you wrote:
>
> > http://www.denx.de/doc/TQM8xxL/debugging.html
>
> I have read it before,but only for module or application,
> not for kernel and ppcboot,someone told me because of
> ppcboot's relocation,so it is difficult in some externd
On Tue, Aug 27, 2002 at 01:52:34AM +0530, Aman wrote:
>
> Hi
>
> I have build a linux image for IBM PPC 440 using the
> src-linuxppc_2_4_devel.tar.bz2 [Powerpc Kernel Source] taken from the
> website http://www.ppckernel.org/tree.php?id=5. Now I want to download the
> image to the IBM PPC 440 eval
>I'm digging in the 823e book for any registers that may need to be changed.
>-Jason
Which port are you using?
How are you configuring it?
Do you have the all the peripherals turned off?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
>>eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
>>IP-Config: Incomplete network configuration information.
>
> You are passing bad/insufficient boot arguments to the Linux kernel;
> unfortunaltely you don;t show us this part of the boot messages, so I
> cannot even guess what y
On Thu, Aug 22, 2002 at 11:09:19AM -0700, Armin Kuster wrote:
>
> David,
>
> The whole phy idea back when I did it was modeled after the fec.c driver
> with the thought that at some point we could merge all phy_info structs
> into a common file. The same idea was applied to the mii routines. I
>
Hi everybody,
I'm designing a custom board based on an MPC860T processor (MPC860T, flash,
SDRAM, serial ports, LTX971A and SpartanII).
I'm looking for someone who could verify my design (you would of course be
paid for the service). The schematic capture tool I use is Protel.
Thanks in advance.
> After running ppcboot on our board successfully (including the fast
> ethernet LXT972), we have trouble on enabling FEC on linux kernel. The
> problem is that we cannot send any packets through the network after the
> kernel is booted. The ethernet looks OK during initialization according
> to t
On Sat, 2002-08-24 at 02:05, Vishwanath wrote:
>
> By going through the code, I understood that ioremap64() is used for mapping
> the 36-bit real address onto 32-bit effective address space. How this
> mapping information is conveyed to user applications ?
I don't understand the question. Do you
Hollis,
At 08:48 AM 8/26/2002, you wrote:
>The usual(32-bit) way is to mmap(/dev/mem). I don't know if that will work
>with
>36-bit addresses.
It will work only for first 4G of physical address space.
/dev/mem cannot be used to access EPB/OCP or PCI address space on 440.
For this purpose "/dev
16 matches
Mail list logo
