PCMCIA cards for MPC8xx?
Fanny Wakizaka wrote: >Hi, >We are developing a custom hw based on the MPC855 with support to PCMCIA. We >are using MontaVista linux kernel 2.4.17. >Could you give me some suggestions of PC Cards that worked with MPC8xx? I'm >looking for ethernet cards, modem cards and wireless cards. >Thanks in advance, >Fanny > I have used: cisco 340/350 and lucent wlan cards, 3com 3c589 lan cards, and modems cards do not work. The problem with modem cards had something to do with a dependancy on serial.c (8xx uses arch/ppc/8xx_io/uart.c). I don't remember the exact problem now. > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Machine Check error in Embedded Planet Board
Narendra wrote: > > Hi All, > > I am working on WLAN driver for Embedded Planet RPXLITE board on > Hard Hat Linux 2.0. > > When i start a ping session of packet size 1400 or above. > Initially it works fine and after responding to around 200 > packets, there is a machine check error occuring in function > in_be16(). > > NIP --- points to the routine where i will be in loop to read the > received data. > > Any idea why this is happening?? > Is this any problem with Kernel or with Embedded Planet board? Try disabling bus timeouts. > > > Thanks in Advance, > Naren > > Here is the oops message that i get everytime, > Machine check in kernel mode. > Caused by (from SRR1=9032): Unknown values in msr > Oops: machine check, sig: 7 > NIP: C56784CC XER: C000197F LR: C567849C SP: C0129E20 REGS: > c0129d70 TRAP: 0200 > MSR: 9032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 > TASK = c0128010[0] 'swapper' Last syscall: 120 > last math last altivec > GPR00: 0498 C0129E20 C0128010 801C 02C1 > C3CA8800 > GPR08: 8036 0100 0498 3637 35F33F93 1001B8DC > FF76FFDF BFBBFE7F > GPR16: FDFF BFFF FFEF FEFF 1032 00129EF0 > 0036 > GPR24: 0018 05D8 C3F87604 C3CA8C98 C3F87400 > 801C 001C > Call backtrace: > C567849C C5676A78 C5674D94 C0003904 C0003A30 C0002810 C0003F84 > C0003F98 C01367C0 C00021E4 > Kernel panic: Aiee, killing interrupt handler > > In interrupt handler - not syncing > Rebooting in 180 seconds.. > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
symbol card with orinoco_cs on mpc823
On Thursday, August 1, 2002, at 11:23 PM, David Gibson wrote: > > On Fri, Aug 02, 2002 at 02:01:52PM +0800, shaowei dai wrote: >> >> Hello, >> >> Has anybody tried orinodo_cs 0.11b or 0.12b with success on symbol >> Spectrum24 High rate11M card on mpc platform? >> I've tried 2.4.18-pre3 and 2.4.19-rc3 kernel with orinoco driver. It >> works >> fine with intersil card. But >> when i try it on symbol card, it always crashes. After tracing down i >> find >> it is caused by hermes_init(). It seems the >> call to hermes_write_regn(hw,INTEN,0) cause the crash. The ksymoops >> also >> suggest this function. It is just an io write. What can be wrong? And >> most >> strange thing is why it doesn't cause any trouble in normal intersil >> card. > > That's wierd - it is just a register write, so this sounds like a > low-level problem. Is something about the card confusing the PCMCIA > system so it's reporting the wrong IO addresses? Or maybe the timing > is a little bit different and something in the slot driver can't cope. > I would guess timing. I have seen problems between different cards with the same chipset fail on 8xx. Usually timing is the culprit. > -- > David Gibson | For every complex problem there is a > david at gibson.dropbear.id.au| solution which is simple, neat and > | wrong. > http://www.ozlabs.org/people/dgibson > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
idle for m8xx
Michael Meriin wrote: >Hi there, > >In all last kernels idle mode for m8xx is implemented as an endless loop. >Therefore the idle modes of the m8xx family are not used. >Implementation of the internal Idle modes of the m8xx family will >significantly reduce >the power consumption in the embedded systems. >Does anybody know how to do this? > The ARM kernel does it quite well. Basically, they have an abstraction in the idle loop where you can plug in sub-arch/processor specific code that puts the processor into the idle state. 4xx has idles states that differ from the rest of the ppc family as well. It would be nice to move the power_save routine into the platform code allowing each sub-arch/processor to define its own. I have plans on doing exactly that in the near future, but if you beat me to it > >Best Regards, > Michael Meriin > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
LMBench and CONFIG_PIN_TLB
Paul Mackerras wrote: >>btw, there are bugs with it. Starting several processes with init or >>even telnetd will expose the bug. >> > >David and I haven't been able to reproduce this on the Walnut or the >EP405. What sort of machine are you using, what processor, how much >RAM, and what distro are you using? > >Paul. > I run MVL (of course) on a walnut with 32MB of RAM. What is your environment? btw, MVL uses soft-float in glibc not floating point emulation in the kernel. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
LMBench and CONFIG_PIN_TLB
Dan Malek wrote: > > Paul Mackerras wrote: > > >> I suspect we are all confusing two things here: (1) having pinned TLB >> entries and (2) using large-page TLB entries for the kernel. > > > I wasn't confusing them :-). I know that large page sizes are > beneficial. > Someday I hope to finish the code that allows large page sizes in the > Linux page tables, so we can just load them. > >> We could have (2) without pinning any TLB entries but it would take >> more code in the TLB miss handler to do that. > > > Only on the 4xx. I have code for the 8xx that loads them using the > standard lookup. Unfortunately, I have found something that isn't quite > stable with the large page sizes, but I don't know what it is. > > >> It is an interesting >> question whether the benefit of having the 64th TLB slot available for >> applications would outweigh the cost of the slightly slower TLB >> misses. > > > Removing the entry will increase the TLB miss rate by 1/64 * 100 percent, > or a little over 1.5%, right? Any application that is thrashing the TLB > cache by removing one entry is running on luck anyway, so we can't > consider > those. When you have applications using lots of CPU in user space (which > is usually a good thing :-), increased TLB misses will add up. > >> My feeling is that it would be a close-run thing either way. > > > So, if you have a product that runs better one way or the other, just > select the option that suits your needs. If the 4xx didn't require the > extra code in the miss handler to fangle the PTE, large pages without > pinning would clearly be the way to go (that's why it's an easy decision > on 8xx and I'm using it for testing). > >> Were you using any large-page TLB entries at all? > > > Yes, but the problem was taking the tlb hit to get the first couple of > pages loaded and hitting the hardware register in time. It was a hack > from the first line of code :-) If you are going to pin a kernel entry, > you may as well map the whole space. I don't think it would even work > if we were loading large pages out of the PTE tables. > >> Tom Rini mentioned the other day that some 8xx processors >> only have 8 (I assume he meant 8 data + 8 instruction). > > > Yes, there are a number of variants now that have everything from 8 to > 64 I believe. It was just easier to pick out the 860 (which always has > lots of entries) for testing purposes. > > The 8xx also has hardware support for pinning entries that basically > emulates BATs. It doesn't require any software changes except for > the initial programming of the MMU control and loading of the pinned > entries. > >> David's suggestion was purely in the context of the 405 >> processor, which has 64. > > > There is an option to enable it, so just enable it by default. What > do you gain by removing the option, except the possibility to prevent > someone from using it when it may be to their benefit? It certainly > isn't a proven modification, as there may be some latent bugs associated > with dual mapping pages that may be covered by the large page and > some other mapping (I think this is the problem I see on the 8xx). btw, there are bugs with it. Starting several processes with init or even telnetd will expose the bug. > > >> (actually, why is there the "860 >> only" comment in there?) > > > Because the MMU control registers are slightly different among the 8xx > processor variants, and I only wrote the code to work with the 860 :-) > > Thanks. > > > -- Dan > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
AW: Does anyone port m8xx_pcmcia driver to Linux Kernel successfully?
The m8xx socket driver did not get loaded. Turn on some debug in the
pcmcia code. What is your h/w?
Jacky Wang wrote:
>Hi all,
>
>I tried the patch with standard linux kernel 2.4.18 with hand-patching.
>
>I can re-compile with the patch (link into the kernel image, not load as a
>module).
>But, while I attach a ne2000 compatible pcmcia card, it looks can't load the
>ethernet card driver or can't detect the card.
>
>here is the pcmcia card I used: Zonet 10Base Ethernet Card.
>
>the attachment is the image I load into by ppcboot 1.1.4 and the log file.
>
>Jacky
>
>>-Original Message-
>>From: owner-linuxppc-embedded at lists.linuxppc.org
>>[mailto:owner-linuxppc-embedded at lists.linuxppc.org]On Behalf Of
>>Sven Boehringer
>>Sent: Thursday, April 25, 2002 5:34 PM
>>To: Matthew Locke; Fend Matthias; jimmlin at solomon.com.tw; linuxppc
>>Subject: Re: AW: Does anyone port m8xx_pcmcia driver to Linux
>>Kernel successfully?
>>
>>
>>
>>Hi all,
>>
>>i tried your patch, but it seems to me that there are some #defines
>>missing?
>>I try to use the source/kernel on a FADS board, an in that section there
>>is
>>"BCSR1_PCCVPP1". But i can't find this value. I tried to copy some
>>values from ppcboot,
>>but these particular are not there. Are there some special includes?
>>
>>I have the actual linuxppc_2_4_devel source-tree, but i can't find these
>>values.
>>
>>regards
>> Sven
>>
>>Matthew Locke wrote:
>>
>>>here is the patch to add the 8xx pcmcia socket driver to the kernel.
>>>
>>>Fend, Matthias wrote:
>>>
>>>>hello Matthew,
>>>>
>>>>i also tried to do this work - without the desired success
>>>>
>>>>i don't know exactly if my hardware is faulty or my m8xx port ... :-(
>>>>
>>>>so if i could have your version of the pcmcia stuff i would be
>>>>
>>very glad.
>>
>>>>thanks matthias
>>>>
>>>>>-Urspr?ngliche Nachricht-
>>>>>Von: Matthew Locke [SMTP:mlocke at mvista.com]
>>>>>Gesendet am: Dienstag, 16. April 2002 18:50
>>>>>An: Jacky Wang
>>>>>Cc: linuxppc-embedded at lists.linuxppc.org
>>>>>Betreff: Re: Does anyone port m8xx_pcmcia driver to Linux Kernel
>>>>>successfully?
>>>>>
>>>>>
>>>>>Jacky Wang wrote:
>>>>>
>>>>>>Hi everyone,
>>>>>>
>>>>>>I am interesting about how to port m8xx_pcmcia driver to
>>>>>>
>>linux kernel w/
>>
>>>>>MPC850.
>>>>>
>>>>>>Would you mind to share your successful experience with me?
>>>>>>
>>>>>I did (w/ the help of others). It is on its way upstream now. If you
>>>>>need it soon, let me know and I can make it available.
>>>>>
>>>>>>Best Regards
>>>>>>Jacky Wang
>>>>>>
>>>>>>
>>>>>** Sent via the linuxppc-embedded mail list. See
>>>>>
>>http://lists.linuxppc.org
>>
>>>>/
>>>>
>>>+/*
>>>
>>--
>>--- */
>>
>>>+/* FADS Boards from Motorola
>>>
>>*/
>>
>>>+
>>>+#if defined(CONFIG_FADS)
>>>+
>>>+#define PCMCIA_BOARD_MSG "FADS"
>>>+
>>>+static int voltage_set(int slot, int vcc, int vpp)
>>>+{
>>>+ uint reg = 0;
>>>+
>>>+ switch(vcc) {
>>>+ case 0: break;
>>>+ case 33: reg |= BCSR1_PCCVCC0; break;
>>>+ case 50: reg |= BCSR1_PCCVCC1; break;
>>>+ default: return 1;
>>>+ }
>>>+
>>>+ switch(vpp) {
>>>+ case 0: break;
>>>+ case 33:
>>>+ case 50:
>>>+ if(vcc == vpp)
>>>+ reg |= BCSR1_PCCVPP1;
>>>+ else
>>>+ return 1;
>>>+ break;
>>>+ case 120:
>>>+ if ((vcc == 33) || (vcc == 50))
>>>+ reg |= BCSR1_PCCVPP0;
>>>+ else
>>>+ return 1;
>>>+ default: return 1;
>>>+ }
>>>+
>>>+ /* first, turn off all power */
>>>+ *((uint *)BCSR1) &= ~(BCSR1_PCCVCC_MASK | BCSR1_PCCVPP_MASK);
>>>+
>>>+ /* enable new powersettings */
>>>+ *((uint *)BCSR1) |= reg;
>>>+
>>>+ return 0;
>>>+}
>>>+
>>>+#define socket_get(_slot_) PCMCIA_SOCKET_KEY_5V
>>>+
>>>+static void hardware_enable(int slot)
>>>+{
>>>+ *((uint *)BCSR1) &= ~BCSR1_PCCEN;
>>>+}
>>>+
>>>+static void hardware_disable(int slot)
>>>+{
>>>+ *((uint *)BCSR1) |= BCSR1_PCCEN;
>>>+}
>>>+
>>>+#endif
>>>+
>>>
>>** Sent via the linuxppc-embedded mail list. See
>>
>http://lists.linuxppc.org/
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
AW: Does anyone port m8xx_pcmcia driver to Linux Kernel successfully?
Sven Boehringer wrote:
>Hi all,
>
>i tried your patch, but it seems to me that there are some #defines
>missing?
>I try to use the source/kernel on a FADS board, an in that section there
>is
>"BCSR1_PCCVPP1". But i can't find this value. I tried to copy some
>values from ppcboot,
>but these particular are not there. Are there some special includes?
>
>I have the actual linuxppc_2_4_devel source-tree, but i can't find these
>values.
>
The BCSR1_* in the CONFIG_FADS areas are register addresses specific to
the FADS board.
It seems some FADS stuff still hasn't made it into _devel. Here are the
defines I have:
/* Bits of interest in the BCSRs.
*/
#define BCSR1_ETHEN ((uint)0x2000)
#define BCSR1_RS232EN_1 ((uint)0x0100)
#define BCSR1_PCCEN ((uint)0x0080)
#define BCSR1_PCCVCC0 ((uint)0x0040)
#define BCSR1_PCCVPP_MASK ((uint)0x0030)
#define BCSR1_PCCVPP0 ((uint)0x0020)
#define BCSR1_PCCVPP1 ((uint)0x0010)
#define BCSR1_RS232EN_2 ((uint)0x0004)
#define BCSR1_PCCVCC1 ((uint)0x0001)
#define BCSR1_PCCVCC_MASK (BCSR1_PCCVCC0 | BCSR1_PCCVCC1)
#define BCSR4_ETHLOOP ((uint)0x8000) /* EEST Loopback */
#define BCSR4_EEFDX ((uint)0x4000) /* EEST FDX
enable */
#define BCSR4_FETH_EN ((uint)0x0800) /* PHY enable */
#define BCSR4_FETHCFG0 ((uint)0x0400) /* PHY autoneg
mode */
#define BCSR4_FETHCFG1 ((uint)0x0040) /* PHY autoneg
mode */
#define BCSR4_FETHFDE ((uint)0x0200) /* PHY FDX
advertise */
#define BCSR4_FETHRST ((uint)0x00200000) /* PHY Reset */
>
>
>regards
> Sven
>
>Matthew Locke wrote:
>
>>here is the patch to add the 8xx pcmcia socket driver to the kernel.
>>
>>Fend, Matthias wrote:
>>
>>>hello Matthew,
>>>
>>>i also tried to do this work - without the desired success
>>>
>>>i don't know exactly if my hardware is faulty or my m8xx port ... :-(
>>>
>>>so if i could have your version of the pcmcia stuff i would be very glad.
>>>
>>>thanks matthias
>>>
>>>>-Urspr?ngliche Nachricht-
>>>>Von: Matthew Locke [SMTP:mlocke at mvista.com]
>>>>Gesendet am: Dienstag, 16. April 2002 18:50
>>>>An: Jacky Wang
>>>>Cc: linuxppc-embedded at lists.linuxppc.org
>>>>Betreff: Re: Does anyone port m8xx_pcmcia driver to Linux Kernel
>>>>successfully?
>>>>
>>>>
>>>>Jacky Wang wrote:
>>>>
>>>>>Hi everyone,
>>>>>
>>>>>I am interesting about how to port m8xx_pcmcia driver to linux kernel w/
>>>>>
>>>>MPC850.
>>>>
>>>>>Would you mind to share your successful experience with me?
>>>>>
>>>>I did (w/ the help of others). It is on its way upstream now. If you
>>>>need it soon, let me know and I can make it available.
>>>>
>>>>>Best Regards
>>>>>Jacky Wang
>>>>>
>>>>>
>>>>** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org
>>>>
>>>/
>>>
>
>>+/* -
>>*/
>>+/* FADS Boards from Motorola */
>>+
>>+#if defined(CONFIG_FADS)
>>+
>>+#define PCMCIA_BOARD_MSG "FADS"
>>+
>>+static int voltage_set(int slot, int vcc, int vpp)
>>+{
>>+ uint reg = 0;
>>+
>>+ switch(vcc) {
>>+ case 0: break;
>>+ case 33: reg |= BCSR1_PCCVCC0; break;
>>+ case 50: reg |= BCSR1_PCCVCC1; break;
>>+ default: return 1;
>>+ }
>>+
>>+ switch(vpp) {
>>+ case 0: break;
>>+ case 33:
>>+ case 50:
>>+ if(vcc == vpp)
>>+ reg |= BCSR1_PCCVPP1;
>>+ else
>>+ return 1;
>>+ break;
>>+ case 120:
>>+ if ((vcc == 33) || (vcc == 50))
>>+ reg |= BCSR1_PCCVPP0;
>>+ else
>>+ return 1;
>>+ default: return 1;
>>+ }
>>+
>>+ /* first, turn off all power */
>>+ *((uint *)BCSR1) &= ~(BCSR1_PCCVCC_MASK | BCSR1_PCCVPP_MASK);
>>+
>>+ /* enable new powersettings */
>>+ *((uint *)BCSR1) |= reg;
>>+
>>+ return 0;
>>+}
>>+
>>+#define socket_get(_slot_) PCMCIA_SOCKET_KEY_5V
>>+
>>+static void hardware_enable(int slot)
>>+{
>>+ *((uint *)BCSR1) &= ~BCSR1_PCCEN;
>>+}
>>+
>>+static void hardware_disable(int slot)
>>+{
>>+ *((uint *)BCSR1) |= BCSR1_PCCEN;
>>+}
>>+
>>+#endif
>>
>+
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Does anyone port m8xx_pcmcia driver to Linux Kernel successfully?
Jacky Wang wrote: >Hi everyone, > >I am interesting about how to port m8xx_pcmcia driver to linux kernel w/ >MPC850. > >Would you mind to share your successful experience with me? > I did (w/ the help of others). It is on its way upstream now. If you need it soon, let me know and I can make it available. > > >Best Regards >Jacky Wang > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
[PATCH] early serial init
andrew may wrote: >On Thu, Apr 11, 2002 at 02:53:36PM +, Armin wrote: > >>John Tyner wrote: >> >>>I remember seeing something awhile ago about early boots, but I didn't >>>think it was for Walnut. Where is it/would it be? >>> >>>On Thu, 11 Apr 2002, Armin wrote: >>> >>> John Tyner wrote: >> >>David G did something and he hit the head_4xx.S & ppc4xx_setup.c and a >>few header files imb405gp.h >> > >This patch is to remove the need for the BASE BAUD define. If we ever start >trying to get a single kernel to build for multiple 405 boards that run at >various clock rates it becomes helpful to calc the base baud for the serial >ports rather than forcing it at compile time. > ok, let me clean this sentence up a bit... A single kernel for multiple 405 boards does not fit the current design goals of the 4xx port, so I hope there are better reasons for this patch. > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
[PATCH] early serial init
andrew may wrote: >On Thu, Apr 11, 2002 at 02:53:36PM +, Armin wrote: > >>John Tyner wrote: >> >>>I remember seeing something awhile ago about early boots, but I didn't >>>think it was for Walnut. Where is it/would it be? >>> >>>On Thu, 11 Apr 2002, Armin wrote: >>> >>> John Tyner wrote: >> >>David G did something and he hit the head_4xx.S & ppc4xx_setup.c and a >>few header files imb405gp.h >> > >This patch is to remove the need for the BASE BAUD define. If we ever start >trying to get a single kernel to build for multiple 405 boards that run at >various clock rates it becomes helpful to calc the base baud for the serial >ports rather than forcing it at compile time. > This does not fit the current design goals of the 4xx port, so I hope there are better reasons for this patch. > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
EP405 PCI interrupt mapping
David Gibson wrote: >Is the current PCI interrupt mapping stuff for the EP405 >(i.e. ppc405_map_irq() in ep405.c) expected to work, or has it just >been copied from walnut and never updated for ep405? It looks bogus >to me. > I just copied it from the walnut. I didn't get that far. I was told you were going to make it all work;) > >-- >David Gibson | For every complex problem there is a >david at gibson.dropbear.id.au | solution which is simple, neat and > | wrong. -- H.L. Mencken >http://www.ozlabs.org/people/dgibson > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
where can I get pdisk
Alex Zeffertt wrote: > > Sorry for the silly question - but where can I get the sources for > pdisk? I've looked on google, > but every link to them seems to be broken. > why do you want pdisk? parted can do mac partitions. I recommend using parted instead. > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Question on the pcmcia module for ppc
Liu HongXun-a16975 wrote: > Hi, Matthew and all, > The MPC 857T is just the same as MPC 860T, except some little revisions. > The linux we used is hhl 2.0, lsp for RPXLite. > MPC 857T ran at 50MHZ and the bus frequency is 50MHZ. > I set this value as follow: > #define M8XX_BUSFREQ (50 * 100) The rpx-lite is an 823e. You should start with the rpx-cllf lsp which is a 860. However, assuming you don't have pci the io base of 0x800 will work fine. I have only tested Slot A on an 860 board (cllf from EP). > > Am I mising anything here? > Thanks a lot > rolf > > -----Original Message- > From: Matthew Locke [mailto:mlocke at mvista.com] > Sent: 2002?1?5? 3:40 > To: Liu HongXun-a16975 > Cc: linuxppc-embedded at lists.linuxppc.org > Subject: Re: Question on the pcmcia module for ppc > > > Liu HongXun-a16975 wrote: > > >>Hi, all, >>I worked on the PCMCIA module for my MPC 857T based board. >>I downloaded the pcmcia-cs 3.1.29 and modified the file modules/m8xx_pcmcia.c. >>My board uses the SLOT B. What I did are just like the (F)ADS and RPXLite. >>I compiled the resulted pcmcia module and loaded them into linux kernel using >>"insmod". >>1. insmod pcmcia_core.o >>2. insmod m8xx_pcmcia.o >>3. insmod ds.o >>Here comes the problem. >>When I inserted ds.o, the driver tells me that "cs: socket 0 timed out during >>reset" >>I looked through the source code and the debug info. >>I found that a lot of the same messages as follows: >>GetStatus(0) = 0x190 >>... >>Such info come from m8xx_pcmcia.c/m8xx_get_status. It seems that someone >>is not satisfied with the above return value and " get status " again and >>again. >>Then it quit. >> >>Any suggestions are highly appreciated! >>Thanks a lot >> > > > I'm not familiar with the 857T pcmcia, perhaps the timing is different. > Check the timing calculation functions against the 857T UM. > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Question on the pcmcia module for ppc
Liu HongXun-a16975 wrote: > Hi, all, > I worked on the PCMCIA module for my MPC 857T based board. > I downloaded the pcmcia-cs 3.1.29 and modified the file modules/m8xx_pcmcia.c. > My board uses the SLOT B. What I did are just like the (F)ADS and RPXLite. > I compiled the resulted pcmcia module and loaded them into linux kernel using > "insmod". > 1. insmod pcmcia_core.o > 2. insmod m8xx_pcmcia.o > 3. insmod ds.o > Here comes the problem. > When I inserted ds.o, the driver tells me that "cs: socket 0 timed out during > reset" > I looked through the source code and the debug info. > I found that a lot of the same messages as follows: > GetStatus(0) = 0x190 > ... > Such info come from m8xx_pcmcia.c/m8xx_get_status. It seems that someone > is not satisfied with the above return value and " get status " again and > again. > Then it quit. > > Any suggestions are highly appreciated! > Thanks a lot I'm not familiar with the 857T pcmcia, perhaps the timing is different. Check the timing calculation functions against the 857T UM. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Linux on an NCD X Terminal?
Hans Johnson wrote: > > Hi Folks, > > Just wondering if anyone has attempted a port of PPC Linux to the NCD EXplora X Terminals? I just picked one up cheap ($10) and upon opening > it up, discovered that it seems to be constructed out of essentially > standard components. > > it has a PPC 403GCX CPU, an S3 Trio64 video chipset, an AMD PCNet fast > ethernet chipset, and a National Semiconductor I/O controller. I'm not > sure what it has for a PCMCIA controller, but it does have a slot. > > Anyway, just curious if has attempted this before. I think this could be > a really neat little box, if it had an operating system. :) > I happen to have one on my desk:) I have not tried to boot linux on it yet. The 403 code is in the latest _devel kernel > > EXplora X Terminals? I just picked one up cheap ($10) and upon > opening it up, discovered that it seems to be constructed out of > essentially standard components. > > it has a PPC 403GCX CPU, an S3 Trio64 video chipset, an AMD PCNet > fast ethernet chipset, and a National Semiconductor I/O controller. > I'm not sure what it has for a PCMCIA controller, but it does > have a slot. > > Anyway, just curious if has attempted this before. I think this > could be a really neat little box, if it had an operating system. :) > I happen to have one on my desk:) I have not tried to boot linux on it yet. The 403 code is in the latest _devel kernel. It *should* work but I haven't tested it lately. Let me know if it works. btw, the PCMCIA seems to be a custom pld. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PCMCIA on MPC823e
Kil-Joon Park wrote: > Target System : Embedded Planet Linux Planet (MPC823e, RPX LITE), kernel 2.4.4 > > I would like to use a PCMCIA ethernet card on the target system. > > I tried to install pcmcia-cs-3.1.28 package, but failed... Where did it fail? > > Is the patch needed? Where do I get the patch? There is no patch for 3.1.28 and 2.4.x. > > Please help me ^^; > > Thank you in advance > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
walnut configuration
I don't think your bk pull worked. walnut_setup.c is gone from the
tree. Also, the default configuartion builds and runs fine for me, but
I don't cross-compile.
Peter Barada wrote:
> Has *anyone* gotten the linuxppc_2_4_devel tree to build for a walnut board?
> If so, what did you have to do... I've tried the following:
>
> I've gotten a BK resync of the linuxppc_2_4_devel tree as of today and
> attempted to:
>
> 1) edit top level makefile to redefine ARCH to ppc, set CROSS_COMPILE
>to my tool prefix
> 2) make mkproper
> 3) make walnut_config
> 4) make oldconfig
> 5) make dep
> 6) make
>
> This fails while trying to build head_4xx.S since
> CONFIG_PPC601_SYCN_FIX is set in .config when it shouldn't be.
>
>
> After getting past that, it fails next while trying to compile
> ppc4xx_pic.c with:
>
> powerpc-linux-gcc -D__KERNEL__
> -I/home/pbarada/work/penguinppc/linuxppc_2_4_devel.export.3/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common -D__powerpc__ -fsigned-char -msoft-float
> -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -mcpu=403-c -o
> ppc4xx_pic.o ppc4xx_pic.c
> {standard input}: Assembler messages:
> {standard input}:83: Error: unsupported relocation type
> {standard input}:84: Error: unsupported relocation type
> {standard input}:111: Error: unsupported relocation type
> {standard input}:128: Error: unsupported relocation type
> {standard input}:145: Error: unsupported relocation type
> {standard input}:149: Error: unsupported relocation type
> {standard input}:64: Error: unsupported relocation type
> make[1]: *** [ppc4xx_pic.o] Error 1
> make[1]: Leaving directory
> `/home/pbarada/work/penguinppc/linuxppc_2_4_devel.export.3/arch/ppc/kernel'
>
> This is caused by in include/asm-ppc/processor.h, the following needs
> to be change from:
>
> #include
>
> to:
>
> #ifdef CONFIG_4xx
> #include
> #endif
> #ifdef CONFIG_8xx
> #include
> #endif
>
>
> Now it gets past ppc4xx_pic.c, and now blows up compilling walnut_setup.c
> with:
>
> powerpc-linux-gcc -D__KERNEL__
> -I/home/pbarada/work/penguinppc/linuxppc_2_4_devel.export.3/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common -D__powerpc__ -fsigned-char -msoft-float
> -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -mcpu=403-c -o
> walnut_setup.o walnut_setup.c
> In file included from walnut_setup.c:22:
> /home/pbarada/work/penguinppc/linuxppc_2_4_devel.export.3/include/linux/interrupt.h:
> In function `tasklet_disable_nosync':
> /home/pbarada/work/penguinppc/linuxppc_2_4_devel.export.3/include/linux/interrupt.h:174:
> warning: implicit declaration of function `smp_mb'
> /home/pbarada/work/penguinppc/linuxppc_2_4_devel.export.3/include/linux/interrupt.h:
> At top level:
> /home/pbarada/work/penguinppc/linuxppc_2_4_devel.export.3/include/linux/interrupt.h:224:
> parse error before `global_bh_lock'
> /home/pbarada/work/penguinppc/linuxppc_2_4_devel.export.3/include/linux/interrupt.h:224:
> warning: type defaults to `int' in declaration of `global_bh_lock'
> /home/pbarada/work/penguinppc/linuxppc_2_4_devel.export.3/include/linux/interrupt.h:224:
> warning: data definition has no type or storage class
> walnut_setup.c: In function `walnut_init':
> walnut_setup.c:115: warning: assignment from incompatible pointer type
> walnut_setup.c: In function `walnut_setup_residual':
> walnut_setup.c:170: structure has no member named `bi_intfreq'
> walnut_setup.c:171: structure has no member named `bi_busfreq'
> walnut_setup.c: At top level:
> walnut_setup.c:234: conflicting types for `walnut_time_init'
> walnut_setup.h:43: previous declaration of `walnut_time_init'
> walnut_setup.c: In function `walnut_calibrate_decr':
> walnut_setup.c:286: structure has no member named `bi_intfreq'
> walnut_setup.c:288: `decrementer_count' undeclared (first use in this
> function)
> walnut_setup.c:288: (Each undeclared identifier is reported only once
> walnut_setup.c:288: for each function it appears in.)
> walnut_setup.c:289: `count_period_num' undeclared (first use in this function)
> walnut_setup.c:290: `count_period_den' undeclared (first use in this function)
> make[1]: *** [walnut_setup.o] Error 1
> make[1]: Leaving directory
> `/home/pbarada/work/penguinppc/linuxppc_2_4_devel.export.3/arch/ppc/kernel'
>
> At this point I thought I'd ask.
>
>
> --
> Peter Barada Peter.Barada at motorola.com
> Wizard 781-852-2768 (direct)
> WaveMark Solutions(wholly owned by Motorola) 781-270-0193 (fax)
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Problems with Sandpoint and IDE access
hmm, I should have looked at your boot messages closer. The IDE driver does not see a hard drive. Do you have the right options turned on in the kernel? Claire Troussier wrote: > It already exists with major 3 and minor 0 > > Matthew Locke a ?crit : > > >> you probably are missing /dev/hda . Try "MAKEDEV hda" in the /dev >> directory. >> >> Claire Troussier wrote: >> >> >>> Hi, >>> >>> I am using Montavista 2.4.2_hhl20 with a Sanpoint (8240) board and I am >>> trying to add a hard disk on the IDE interface. I include the IDE driver >>> in my kernel and I boot using an ethernet board. The driver seems to be >>> correctly initialized but when I try to access the hard disk I always >>> got the same error message >>> >>> sh-2.03# fdisk /dev/hda >>> >>> Unable to open /dev/hda >>> sh-2.03# >>> >>> Any idea ? >>> >>> Thanks for your help. >>> >>> Claire >>> >>> Here are the boot messages >>> >>> Linux/PPC load: >>> Uncompressing Linux...done. >>> Now booting the kernel >>> Total memory = 16MB; using 0kB for hash table (at ) >>> Linux version 2.4.2_hhl20 (claire at claire) (gcc version 2.95.2 19991030 >>> (2.95.3 p >>> rerelease/franzo)) #48 lun sep 10 16:41:47 CEST 2001 >>> Motorola SPS Sandpoint Test Platform >>> Sandpoint port (C) 2000, 2001 MontaVista Software, Inc. >>> (source at mvista.com) >>> On node 0 totalpages: 4096 >>> zone(0): 4096 pages. >>> zone(1): 0 pages. >>> zone(2): 0 pages. >>> Kernel command line: >>> OpenPIC Version 1.2 (1 CPUs and 24 IRQ sources) at f7fd >>> time_init: decrementer frequency = 24.997563 MHz >>> Calibrating delay loop... 166.29 BogoMIPS >>> Memory: 14600k available (968k kernel code, 436k data, 72k init, 0k >>> highmem) >>> Dentry-cache hash table entries: 2048 (order: 2, 16384 bytes) >>> Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) >>> Page-cache hash table entries: 4096 (order: 2, 16384 bytes) >>> Inode-cache hash table entries: 1024 (order: 1, 8192 bytes) >>> POSIX conformance testing by UNIFIX >>> PCI: Probing PCI hardware >>> CI: device 00:11.0 has unknown header type 7f, ignoring. >>> Linux NET4.0 for Linux 2.4 >>> Based upon Swansea University Computer Society NET3.039 >>> Starting kswapd v1.8 >>> pty: 256 Unix98 ptys configured >>> block: queued sectors max/low 9637kB/3212kB, 64 slots per queue >>> Uniform Multi-Platform E-IDE driver Revision: 6.31 >>> ide: Assuming 33MHz system bus speed for PIO modes; override with >>> idebus=xx >>> W82C105: IDE controller on PCI bus 00 dev 59 >>> W82C105: chipset revision 5 >>> W82C105: 100% native mode on irq 17 >>> ide0: BM-DMA at 0xbfffd0-0xbfffd7, BIOS settings: hda:pio, hdb:pio >>> SL82C105 command word: 5 >>> IDE timing: 0909, resetting to PIO0 timing >>> ide1: BM-DMA at 0xbfffd8-0xbfffdf, BIOS settings: hdc:pio, hdd:pio >>> SL82C105 command word: 5 >>> IDE timing: 03e4, resetting to PIO0 timing >>> Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ >>> SERIAL_PCI ena >>> bled >>> ttyS00 at 0x03f8 (irq = 4) is a 16550A >>> ttyS01 at 0x02f8 (irq = 3) is a 16550A >>> 8139too Fast Ethernet driver 0.9.13 loaded >>> eth0: RealTek RTL8139 Fast Ethernet at 0xbf00, 00:50:fc:21:19:ca, >>> IRQ 18 >>> NET4: Linux TCP/IP 1.0 for NET4.0 >>> IP Protocols: ICMP, UDP, TCP >>> IP: routing cache hash table of 512 buckets, 4Kbytes >>> TCP: Hash tables configured (established 1024 bind 1024) >>> Sending BOOTP requests OK >>> IP-Config: Got BOOTP answer from 192.168.254.20, my address is >>> 192.168.254.203 >>> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. >>> Looking up port of RPC 13/2 on 192.168.254.20 >>> Looking up port of RPC 15/2 on 192.168.254.20 >>> VFS: Mounted root (nfs filesystem) readonly. >>> Freeing unused kernel memory: 72k init 4k openfirmware >>> INIT: version 2.77 booting >>> INIT: Entering runlevel: 3 >>> sh-2.03# >>> >>> >>> sh-2.03# cat /proc/pci >>> PCI devices found: >>> Bus 0, device 0, function 0: >>> Class 0600: PCI device 1057:0003 (rev 17). >>> Master Capable. Latency=32. >>> Prefetchable 32
Status on 403 (Oak) support
Hatle and I have 403GCX code against the latest _devel tree that doesn't quite work yet. I can post a patch over the weekend for people that want to play with it. Might as well play with the latest stuff and make that work:) Grant Erickson wrote: > On Fri, 14 Sep 2001, Donovan, Chris wrote: > >>> Yes, when I merged the latest bunch of 405GP changes I did break >>> some of the 403 support. >> >> When was the last time that support for the 403 was working? Where can >> I get a copy of the source code at that point? I understand if there >> might be new features that would be missing but I'd like to see if I >> can get something working. Thanks. Chris > > > It's horrendously out-of-date (by nearly two years) as I've not worked on > it since MontaVista took over the 405GP work; however, if it serves as a > historical perspective and starting point to resurrect the 403GCX support, > great: > > http://www.borg.umn.edu/~grant/Linux/index.html > > Regards, > > Grant Erickson > > > -- > Grant Erickson University of Minnesota Alumni > o mail:erick205 at umn.edu 1996 BSEE > o http://www.umn.edu/~erick205 1998 MSEE > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Problems with Sandpoint and IDE access
you probably are missing /dev/hda . Try "MAKEDEV hda" in the /dev directory. Claire Troussier wrote: > Hi, > > I am using Montavista 2.4.2_hhl20 with a Sanpoint (8240) board and I am > trying to add a hard disk on the IDE interface. I include the IDE driver > in my kernel and I boot using an ethernet board. The driver seems to be > correctly initialized but when I try to access the hard disk I always > got the same error message > > sh-2.03# fdisk /dev/hda > > Unable to open /dev/hda > sh-2.03# > > Any idea ? > > Thanks for your help. > > Claire > > Here are the boot messages > > Linux/PPC load: > Uncompressing Linux...done. > Now booting the kernel > Total memory = 16MB; using 0kB for hash table (at ) > Linux version 2.4.2_hhl20 (claire at claire) (gcc version 2.95.2 19991030 > (2.95.3 p > rerelease/franzo)) #48 lun sep 10 16:41:47 CEST 2001 > Motorola SPS Sandpoint Test Platform > Sandpoint port (C) 2000, 2001 MontaVista Software, Inc. > (source at mvista.com) > On node 0 totalpages: 4096 > zone(0): 4096 pages. > zone(1): 0 pages. > zone(2): 0 pages. > Kernel command line: > OpenPIC Version 1.2 (1 CPUs and 24 IRQ sources) at f7fd > time_init: decrementer frequency = 24.997563 MHz > Calibrating delay loop... 166.29 BogoMIPS > Memory: 14600k available (968k kernel code, 436k data, 72k init, 0k > highmem) > Dentry-cache hash table entries: 2048 (order: 2, 16384 bytes) > Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) > Page-cache hash table entries: 4096 (order: 2, 16384 bytes) > Inode-cache hash table entries: 1024 (order: 1, 8192 bytes) > POSIX conformance testing by UNIFIX > PCI: Probing PCI hardware > CI: device 00:11.0 has unknown header type 7f, ignoring. > Linux NET4.0 for Linux 2.4 > Based upon Swansea University Computer Society NET3.039 > Starting kswapd v1.8 > pty: 256 Unix98 ptys configured > block: queued sectors max/low 9637kB/3212kB, 64 slots per queue > Uniform Multi-Platform E-IDE driver Revision: 6.31 > ide: Assuming 33MHz system bus speed for PIO modes; override with > idebus=xx > W82C105: IDE controller on PCI bus 00 dev 59 > W82C105: chipset revision 5 > W82C105: 100% native mode on irq 17 > ide0: BM-DMA at 0xbfffd0-0xbfffd7, BIOS settings: hda:pio, hdb:pio > SL82C105 command word: 5 > IDE timing: 0909, resetting to PIO0 timing > ide1: BM-DMA at 0xbfffd8-0xbfffdf, BIOS settings: hdc:pio, hdd:pio > SL82C105 command word: 5 > IDE timing: 03e4, resetting to PIO0 timing > Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ > SERIAL_PCI ena > bled > ttyS00 at 0x03f8 (irq = 4) is a 16550A > ttyS01 at 0x02f8 (irq = 3) is a 16550A > 8139too Fast Ethernet driver 0.9.13 loaded > eth0: RealTek RTL8139 Fast Ethernet at 0xbf00, 00:50:fc:21:19:ca, > IRQ 18 > NET4: Linux TCP/IP 1.0 for NET4.0 > IP Protocols: ICMP, UDP, TCP > IP: routing cache hash table of 512 buckets, 4Kbytes > TCP: Hash tables configured (established 1024 bind 1024) > Sending BOOTP requests OK > IP-Config: Got BOOTP answer from 192.168.254.20, my address is > 192.168.254.203 > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. > Looking up port of RPC 13/2 on 192.168.254.20 > Looking up port of RPC 15/2 on 192.168.254.20 > VFS: Mounted root (nfs filesystem) readonly. > Freeing unused kernel memory: 72k init 4k openfirmware > INIT: version 2.77 booting > INIT: Entering runlevel: 3 > sh-2.03# > > > sh-2.03# cat /proc/pci > PCI devices found: > Bus 0, device 0, function 0: > Class 0600: PCI device 1057:0003 (rev 17). > Master Capable. Latency=32. > Prefetchable 32 bit memory at 0x0 [0x]. > Non-prefetchable 32 bit memory at 0x0 [0xfff]. > Bus 0, device 11, function 0: > Class 0601: PCI device 10ad:0565 (rev 16). > IRQ 17. > Bus 0, device 11, function 1: > Class 0101: PCI device 10ad:0105 (rev 5). > IRQ 17. > Master Capable. Latency=128. Min Gnt=2.Max Lat=40. > I/O at 0xb8 [0xbf]. > I/O at 0xb4 [0xb7]. > I/O at 0xbfffe8 [0xbfffef]. > I/O at 0xbfffe4 [0xbfffe7]. > I/O at 0xbfffd0 [0xbfffdf]. > I/O at 0xbfffc0 [0xbfffcf]. > Bus 0, device 15, function 0: > Class 0200: PCI device 10ec:8139 (rev 16). > IRQ 18. > Master Capable. Latency=128. Min Gnt=32.Max Lat=64. > I/O at 0xbffe00 [0xbffeff]. > Non-prefetchable 32 bit memory at 0xbf00 [0xbfff]. > sh-2.03# > > > sh-2.03# cat /proc/ioports > -001f : dma1 > 0020-003f : pic1 > 0040-005f : timer > 0080-008f : dma page reg > 00a0-00bf : pic2 > 00c0-00df : dma2 > 02f8-02ff : serial(auto) > 03f8-03ff : serial(auto) > 00bffe00-00bffeff : PCI device 10ec:8139 > 00bffe00-00bffeff : eth0 > 00bfffc0-00bfffcf : PCI device 10ad:0105 > 00bfffd0-00bfffdf : PCI device 10ad:0105 > 00bfffd0-00bfffd7 : ide0 > 00bfffd8-00bfffdf : ide1 > 00bfffe4-00bfffe7 : PCI device 10ad:0105 > 00bfffe8-00bfffef :
Status on 403 (Oak) support
lets move this to the list it belongs on...
Donovan, Chris wrote:
> I'm trying to run linux on a board with a 403GCX processor on it. I ran into
> an error while trying to compile the kernel as follows:
>
> {standard input}: Assembler messages:
> {standard input}:83: Error: unsupported relocation type
> {standard input}:84: Error: unsupported relocation type
> {standard input}:111: Error: unsupported relocation type
> {standard input}:128: Error: unsupported relocation type
> {standard input}:145: Error: unsupported relocation type
> {standard input}:149: Error: unsupported relocation type
> {standard input}:64: Error: unsupported relocation type
> make[1]: *** [ppc4xx_pic.o] Error 1
> make[1]: Leaving directory `/d/ctemp/src/src-linuxppc_2_4/arch/ppc/kernel'
> make: *** [_dir_arch/ppc/kernel] Error 2
>
> While searching the archives I found a thread which mentioned that that
> kernel no longer compiles for the 403 processor and there was no mention of
> a solution to the problem. Which version of the kernel should work on the
> 403GCX? Thanks for your help.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
AW: CPCI-405 port (PPC405GP)
Stefan Roese wrote: >>> Please find attached a port to our CPCI-405 board >> >> Nice job, but did you actually get your system booted? There is >> something generically wrong with the 405 port, and it's been a pain >> in the ass trying to find it. If you actually booted a system >> that ran properly, it would be interesting to know what you used for >> a file system. > > > I get my system booted up to the busybox prompt via nfs root file system. > After this most commands do nothing at all (as described from andrew may > "405GP booting"), and the system hangs pretty soon :-(. > > I would think that the walnut port is behaving this way too, am I right? > no, I pulled this morning and the walnut works fine. I am using nfs root with HHL2.0 userland. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
SysVInit (RC Scripts) on HHL 2.0
sounds like a user error during installation. try using the installer, otherwise you have to figure out the dependancies by hand. James F Dougherty wrote: > Hi, > > I am using HHL 2.0 (2.4.2) on MPC8240 and I downloaded > the root filesystem RPM's from > > ftp://ftp.mvista.com/pub/Journeyman/cd2/ppc_82xx/apps/*.rpm > > and installed them on my root filesystem. > > Question: How come none of the init scripts work? > > I have to run: > > devfsd /dev > mount -a > > every time I boot. It spawns a getty, but none of the rc > files get called ... > > > Is there some bug in HHL 2.0 on ppc_82xx I don't know about? > > Thanks, > -James > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Is there a PCI based 802.11b device driver for ppc linux?
Tom Rini wrote: > On Fri, Aug 17, 2001 at 11:11:28AM +0800, Liu HongXun-a16975 wrote: > >> Hi, all, >> Our customized ppc based board only has PCI interface. I wonder if there is >> a PCI based 802.11b device driver for ppc linux? > > > Well, it depends on the chipset. And is it a PCI one or a pcmcia one in a > pcmcia pci card. I think some of the prism II and whatnot based cards work. > Take a look in drivers/net/wireless. > Both the prism II and Cisco PCI cards have device drivers. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Loading Hard Hat 2.0
Tom Rini wrote: > On Wed, Aug 15, 2001 at 01:33:56PM -0700, clark at esteem.com wrote: > > >> Has anybody loaded Hard Hat 2.0 Linux Journeyman edition on Red >> Hat 7.1 yet? I know its been asked before, but I was wondering if >> the answer has changed from no. > > > RedHat 7.1 is not a supported target. See below. > > >> Is there an easy way to install Hard Hat 2.0 without removing my >> 1.0 install? > > > Normally, yes. But, I _think_ the main reason RedHat 7.1 isn't > supported is that the version of RPM shipped by default does NOT > support relocation, so you can't install HHL 2.0 into another > subdir and have 1.x and 2.0 co-exist. > If relocation is not a big deal, you can either fake out our installer or install by hand (use rpm). To fake out the installer I think you just change /etc/redhat-release to 7.0 instead 7.1. Of course, change it back once the install finishes:) ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
CFI flash support for AMD chips
Navin Boppuri wrote: > Hello, > > I am trying to use the CFI flash support for AMD chips. I selected the > CFI support in kernel configuration and defined the flash memory map on > my board ( CFI Flash device in Physical memory map). I see that CFI is > able to find the flash devices on my board correctly. Now, do I need to > create a /dev/flash device in the dev directory? What Major, Minor > numbers do I use? How do I actually use this driver??? > check out the MTD home page. http://www.linux-mtd.infradead.org ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PCMCIA - MPC860T
Gerhard TAEUBL wrote: > Hi! > > I want to get run my pcmcia port with a flash disk (SANDISK). Well > pcmcia works fine (expect connect - reconnet,but this isn't > important for me yet). I also added the IDE stuff, I can compile > everthing and boot, but how I have to mount the disk (maybe a silly > question, but I don't have any more ideas...) > It looks like a normal IDE drive, so just partition it and then mount it. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Is 802.11b supported by ppc linux?
Liu HongXun-a16975 wrote: > Hi, all, Is 802.11b supported by ppc linux? thanks Rolf Simple question, simple answer. Yes 802.11b is supported by ppc linux. I have used Cisco, wavelan, and prismII sucessfully on many different ppc platforms. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
New Linux PowerPC development
Cindy Peters wrote: > We have just recently been instructed by management to stay with the > MPC823 in order to re-use the previous software and hardware > development as much as possible. We are looking at using some VHDL > IP provided by Open Cores (this is very new) for the IDE interface. > Are you familiar with this? > > The VHDL code uses a processor independent interface called a > wishbone interface. I don't know much about it yet. I don't know if > this is something standard or just developed for Open Cores. Do > you (or anyone else) know of any driver software that may be > available for this interface? > Having done several non-standard IDE interfaces before, I can say PIO mode for the IDE OpenCore would be straight forward to implement. DMA is always a bit more complicated. I took a quick look thru the OpenCore documentation. It looks like the core would work on the 8xx bus with few modifications. > I have downloaded the lmbench software to determine some benchmarking information. I am not sure how to build it for the PPC. I have a cross > compiler development environment setup in a subdirectory. Can someone help > me with this? Sure, download our Journeyman product for 8xx, it includes cross-compilers and 8xx userland. ftp://ftp.mvista.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
New Linux PowerPC development
Grant Erickson wrote: > On Tue, 31 Jul 2001, Cindy Peters wrote: > >> I have downloaded the lmbench software to determine some benchmarking >> information. I am not sure how to build it for the PPC. I have a cross >> compiler development environment setup in a subdirectory. Can someone >> help me with this? > > > MontaVista reportedly has this as part of their at-cost HHL kit. However, > I am not aware of any monetarily-free bundles of this cross-compiled for > various architectures. Our tool-chain is publicly available on our ftp site for several architectures (including 8xx). ftp://ftp.mvista.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Segmentation fault while dynamic linking
Justin (Gus) Hurwitz wrote: > On Thu, 28 Jun 2001, Michael Habermann wrote: > > >>At 10:08 AM 6/27/2001 -0700, Matthew Locke wrote: >> >> >>>There are two places cacheline size affects glibc. The one above that >>>you already found and in the glibc ppc optimized memset or memcpy (don't >>>remember which one). you can just delete the ppc specific memset and >>>configure will pull in the generic memset. >>> >>Yeah, deleting memset.S solved my problem. >> >>Thanks to you and the guys who answered by private mail. >> > > Could you post a quick summary of what yo had to do to get this to work > (ie, which source you downloaded, which patches you downloaded and > applied, and which flags you used to compile)? > > I've been trying to get uClibc to work, but am having IO errors with it, > so I'm thinking of giving glibc another try. > that is probably best:-) Just grab our toolchain it works and it has the patches in its src rpm. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Serial Port problem with 823e on Embedded Planet
Pergola, Michael wrote: >>You could switch to use SCC's instead. We have a modified driver that >>supports full HW handshake on all SCC's (and you can configure the >>number and size of I/O buffers to optimize for throughput). >> >> > [Pergola, Michael] Is that the patch commproc.c.patch.gz dated > 07/20/2000? > > > If you use both SCCs for uarts, you lose ethernet. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Segmentation fault while dynamic linking
Michael Habermann wrote: >My configuration: Kernel 2.4.4, glibc 2.2.2, bash 2.05, FADS, MPC855T > > ... > >>>binutils 2.11.2 >>>gcc 2.95.3 >>>glibc 2.2.2 >>> >>>Everything unpatched and downloaded from ftp.gnu.org. >>> >> >>From what I read in the mailing list, I would also say it looks like this > problem. > > I've recompiled my toolchain now with plain gnu software and the following > patches > from ftp.mvista.com and glibc-src package: > glibc22-27.patch glibc22-getaddrinfo.dpatch > glibc22-disable-static.dpatch glibc22-nss-upgrade.dpatch > glibc22-eo_EO.dpatch glibcbug.dpatch > > But the problem is still there. > > I couldn't find 'the cacheline patch'. Is it the one mentioned here: > http://lists.linuxppc.org/listarcs/linuxppc-embedded/23/msg00073.html > There are two places cacheline size affects glibc. The one above that you already found and in the glibc ppc optimized memset or memcpy (don't remember which one). you can just delete the ppc specific memset and configure will pull in the generic memset. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Segmentation fault while dynamic linking
Michael Habermann wrote: > At 10:12 AM 6/26/2001 -0700, Matthew Locke wrote: > >>> My configuration: Kernel 2.4.4, glibc 2.2.2, bash 2.05, FADS, MPC855T >> >> >> who's toolchain are you using? glibc 2.2.x has a cacheline size bug >> for the smaller cacheline ppc processors. Our toolchain has a fix for >> it. grab our HHL 2.0 Journeyman edition and give it a try. >> http://www.mvista.com > > > binutils 2.11.2 > gcc 2.95.3 > glibc 2.2.2 > > Everything unpatched and downloaded from ftp.gnu.org. yeah, sounds like the cacheline problem. It is still in glibc 2.2.2 and 2.2.3. > > I've read in the mailing list, that the glibc needs to be patched. But > I've found that the most changes are already made at glibc2.2.2, so I > assumed it should work. > > The kernel is 2.4.4 from ftp.denx.de, patched by a patch posted from > Dave Ellis. > > Ok, I try the mvista glibc. > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Segmentation fault while dynamic linking
Michael Habermann wrote: > My configuration: Kernel 2.4.4, glibc 2.2.2, bash 2.05, FADS, MPC855T who's toolchain are you using? glibc 2.2.x has a cacheline size bug for the smaller cacheline ppc processors. Our toolchain has a fix for it. grab our HHL 2.0 Journeyman edition and give it a try. http://www.mvista.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
software FP support?
Our (montavista) toolchain is built with softfloat. Btw, our 2.0 Journeyman release is available on our ftp site (includes glibc-2.2.3). start with our website to find out how to download it. http://www.mvista.com Kumar Gala wrote: > I was wondering what the current state of software floating point support > was in the PowerPC embedded world. > > I am trying to build a glibc with soft-fp to get a /bin/sh that does not > setup the fpu state. I was wondering if someone has already gone through > this trouble or how people have been handling this. > > I know that the kernel has support for soft-fp handling which would allow > userland and libc to still use FP code but that seems expensive. > > Any information would be helpful. > > thanks > > - kumar > > > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Starting usb in RPXlite(mpx850) board
Yoo. Jonghoon wrote: > I'm using Montavista Hardhat linux 2.0(kernel 2.4.3) on > RPXlite board(mpx850). It uses Brad's HCI driver > (m8xxhci.c) > > At first, hci driver does not wanted to be initialized. I looked > inside source codes and found that > m8xxhci_start_controller returns error if partnum of cpu is > not m823. So I skipped partnum checking routine and then > hci drvier initialized. Is there any problem to do this ? uh, I believe so. If I remember correctly, USB is only supported on the 823 rpxlite DW. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
glibc 2.2.x?
The problem we ran into with 2.2.2 was the optimized memset wasn't
aligned properly. We reverted back to the generic memset and haven't
had any trouble on 8xx. I am not aware of any similar issues on the 405,
but...
Denton Gentry wrote:
>
> About 6 weeks ago there were a couple messages on the list
> about glibc 2.2.x and embedded PowerPC. Has anyone made more
> progress?
> I'm trying to use glibc2.2.3 on a Walnut board, and cannot
> start any processes. The MVista glibc-2.1.3 and ld.so.1 work
> fine on this platform. My problem with glibc 2.2.3 looks similar
> to the problems described a few weeks ago (fault when linking
> libraries).
>
> Just for reference, heres what I did to glibc 2.2.3:
>
> I had to move sysdeps/powerpc/fclrexcept.c to the fpu subdirectory,
> as it deals with the FPU (sysdeps/generic/fclrexcept.c will be used
> instead). I also had to remove the fenv_const and fe_nomask references
> from the Makefile.
> So far as I can see __elf_machine_runtime_setup() in
> sysdeps/powerpc/dl-machine.c has been updated to know that
> not all PPCs have 32 byte cache lines, so I left it alone.
> memset.S does still have an assumption about cache line
> size ("subfic rALIGN, rALIGN, 0x20"), so I moved it aside
> to let the generic version be used.
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Wireless Advice
Arturo Nunez wrote: > > Hello: > I have the following board: > > RPX CLLF > Cpu:XPC860TZ > > From Embbeded Planet. > > Now, I need to do some research in Wireless, I was thinking to use > one of these cards: > > - Cisco Aironet 340 Series Card or > - Linksys WPC11 > Cisco 340 works great. Wavelan also works. I have not tried the Linksys card. the 340 and wavelan work out of the box with the latest pcmcia-cs package. Er, actually, the last change I sent to Dave Hinds broke it. I will be fixing that shortly. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
booting from cramfs in flash
Steven Hein wrote: > > My cramfs adventure continues. > > Okay, so I have a cramfs filesystem image creaed created. > Now, how do I tell the kernel to boot using that filesystem > when the filesystem is an image in flash? > > Maybe I'm on the wrong path, but my previous setup used a compressed > kernel and gzip'ed ext2 filesystem as an initial ramdisk, which > also served as my permanent filesystem. So I thought I should > be able to just replace my old initrd with my new cramfs image, > tell the kernel where it is (in flash), and it would go. It turns out that cramfs is not supported for a root fs or initrd. Basically, the kernel checks a hardcoded list of supported filesystems and if the MAGIC number doesn't match it bails. Midori has a patch to add cramfs to this list. I believe it is in thier kernel package. > > But, that's not the case for me so far. If I pass the address in > flash of my cramfs image as the initrd_start > and initrd_end (in R3/R4, the kernel craps out because it can't reuse > the pages where I told it that the initrd lives). > > So,how do I make this connection? Or, do I still need an ext2 > initrd like I used before? If so, then how do I mount the CRAMFS > filesystem that is an image sitting flash? > You can do that too. Actually that is how we do it on the iPaq. You need to enable MTD, so your flash looks like a block device. then 'mount' can mount cramfs images. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
mkcramfs changes to switch endianness
David Blythe wrote: > > Steve Hein wrote: > > > Just out of curiousity, where do you get the source for the transmeta > > changes (their Midora Linux, I assume). I went looking at their > > web site, and the FTP location they pointed to contained a > > midora-1.0.0-beta1*.tar.gz file that was only 36K.where's the real > > thing? that file is just the build structure/files. once you install that you need to download the rest from the apps dir on the ftp site. start at http://midori.sourceforge.net. > > We used this, as a starting point (or one of the other references to > this patch, i just did a google search to find it again). > > http://lwn.net/2001/0118/a/cramfs.php3 That is the patch include with midori. If i remember correctly, it is included in the kernel mlz. mlz is the midori packaging method, basically a tar gz file. > > I was hoping that it was all on sourceforge, but I guess not. We should > finish integrating the endianness changes against this patch pretty > soon. Maybe if someone else knows if there is a more up to date version > around they could let us know. it is all there on sourceforge, just need to dig a little:) ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
mkcramfs changes to switch endianness
cramfs is still endian dependant. Linus has a couple solutions to this problem, but last time I checked he wasn't clear which was the best. go for it and let us know how it turns out. Steven Hein wrote: > > I'm getting ready to try using cramfs in the 2.4.4 kernel. > Anybody done the work to make 'mkcramfs' create a big-endian > image on a little-endian PC? Before I reinvent the wheel, > I'd like to find out if anybody as done it (and would like > to share :) > > Steve > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
MPC8xxFADS support
Michael Habermann wrote: > > I intend to use the MPC8xxFADS board with an 855T. I've read in this > newsgroup several times that the FADS are causing problems. > Which kind of problems do I have to expect? Is PCMCIA supported reliable? > I still don't have a FADS board so I don't know how well PCMCIA works on it. The support for the 860 FADS is in the code. Give it a try and let me know if find any issues. use the latest pcmcia-cs 3.1.26 ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
MPC855 PCMCIA & wvlan_cs
well I have a wavelan gold card working. It turns out the 8xx socket
driver was never passing the interrupt # up to the card services layer
and therefore never reached the card driver. Not sure why, but its
fixed now. The fix will be included in the 3.1.26 release of pcmcia-cs
(beta will be released shortly). If someone needs it before let me
know. So, i have used and tested the following cards
Wireless (802.11b) - aironet/cisco, wavelan gold, skyline
Ethernet - non combo 3com 589
IDE - sandisk, compact flash on pcmcia adapter
bluetooth and microdrive cards are on my WANTTO list, but I don't have
the h/w yet:)
Matthew Locke wrote:
>
> "Mark S. Mathews" wrote:
> >
> > Are they bus timeouts?
>
> No. they are timeout's from the card. I forget the exact sequence but
> its something like
>
> while (!(status bit) && counter < timeout)
> {
> write xmit data out
> check status bit
> increment timeout counter
> }
>
> It seems the timing setup in the 8xx pcmcia registers doesn't match the
> timing needed for the card. therefore writes and reads to the cards
> registers won't work properly.
>
> >
> > On Mon, 2 Apr 2001, Matthew Locke wrote:
> >
> > >
> > > Janne Lintuala wrote:
> > >
> > > > I's trying to use wvlan_cs (from pcmcia-cs-3.1.25) with Lucent/IEEE
> > > > card in MPC855 at 80/40 and HHL kernel 2.2.14 with PCMCIA-patch from
> > > > Montavista and minor modifications for custom card.
> > >
> > > I am trying to get the wavelan card working as well. My setup is a
> > > little different. 823e with 2.4.2 and pcmcia-cs-3.1.24. I got further
> > > than you did. The card initialized fine and I can use ifconfig to
> > > assign an IP address and bring the interface up. However as soon as I
> > > try to transmit packets I get timeout error's. I have seen this
> > > behavior on other wireless cards and it was due to timing. You probably
> > > need to play with the timing that is setup in m8xx_pcmcia.c in
> > > pcmcia-cs.
> > >
> > > let me know if you figure it out before i do.
> > >
> > > The Aironet4800B/Cisco340 and Prism chipset cards work fine. I did find
> > > that the Aironet4800 won't work. I believe due to the timing settings
> > > on the 8xx are incompatible with that card.
> > >
> > > >
> > > > PC Card is found and wvlan_cs module installed, but the
> > > > driver fails at initialization phase to timeout, presumably at
> > > > hcfio_string-function. Other cards (for example serial_cs or 3c589
> > > > seem to work). So, has anyone any ideas what could go wrong with this
> > > > one?
> > > >
> > > > 1. IO-space is initialized to base 0x8100,size 0x3F and 16bit port
> > > >size. (PBR5=0x8100, POR5=0x28024659)
> > > >
> > > > 2. Interrupts are handled, but none occurs during initialization (in
> > > >other drivers interrupts however work).
> > > >
> > > > 3. Accesses to IO-space go to correct area, ie. 0x8100-0x813F.
> > > >Writes to cards registers (for example at address 0x8128) seem
> > > >to work, ie. I can write a word and read it back later.
> > > >
> > > > 4. config.opts includes "include port 0x100-0xfff" and "include memory
> > > >0x8000-0x80ff".
> > > >
> > > > 5. How should the macros IN/OUT_PORT_WORD and IN/OUT_PORT_STRING in
> > > >wvlan_hcfcfg.h be declared? I assume that as below, ie. all
> > > >accesses non-swapping, or am i wrong? At least Lucent documentation
> > > >says so...
> > > >
> > > > (http://bwrc.eecs.berkeley.edu/People/Grad_Students/jbeutel/wavelan_s0005-11-light.htm)
> > > >
> > > > 6. What else could go wrong?
> > > >
> > > > Best Regards,
> > > > Janne Lintuala
> > > >
> > > > #define wvlan_inb(port) in_8((unsigned char
> > > > *)((port)+_IO_BASE))
> > > > #define wvlan_outb(val, port) out_8((unsigned char
> > > > *)((port)+_IO_BASE), (val))
> > > > #define wvlan_inw(port) in_be16((unsigned short
> > > > *)((port)+_IO_BASE))
> > > > #define wvlan_outw(val, port) out_be16((unsigned short
> > > > *)((port)+_IO_BASE), (val))
> > > > #define wvlan_insw(port, buf, ns) _
how to configure LCD as console for RPX-LITE
I don't remember 2.2.13 having a framebuffer driver for the lcd. download the 2.2.14 kernel from ftp.mvista.com we have pre-configured/built kernel rpms for the rpx-lite called lsp's (linux support package). those are a good starting point for configuring for a frame buffer. As for the console part, I have never tried but it should work. Alan Wang wrote: > > Hi, all > I am compiling mpc8xx-2.2.13 for my RPX-LITE(mpc823) board. Now, I want to > use the LCD > as my console but when I enable the frame buffer and virtual terminal by > "make configure", I got > so many "reference undefined" errors when linking. is there anybody succeeded > in this? > how do u configure your kernel? thank you. > > Alan > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Journaling Filesystem?
"Sacha J. Bernstein" wrote: > > Is there a working journaling filesystem that works with PPC linux? What > does everyone alse to do handle the embedded devices that people may just > walk up and unplug? I use ReiserFS on x86, but I've heard that it may not > work with PPC. I haven't tried to check myself... > It's true, ReiserFS doesn't work on ppc. I know people are working on it, but I am not sure where the current info lives. I believe JFFS works on ppc if you have MTD working on your board. Of course, that doesn't help if don't have flash. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
MPC855 PCMCIA & wvlan_cs
"Mark S. Mathews" wrote:
>
> Are they bus timeouts?
No. they are timeout's from the card. I forget the exact sequence but
its something like
while (!(status bit) && counter < timeout)
{
write xmit data out
check status bit
increment timeout counter
}
It seems the timing setup in the 8xx pcmcia registers doesn't match the
timing needed for the card. therefore writes and reads to the cards
registers won't work properly.
>
> On Mon, 2 Apr 2001, Matthew Locke wrote:
>
> >
> > Janne Lintuala wrote:
> >
> > > I's trying to use wvlan_cs (from pcmcia-cs-3.1.25) with Lucent/IEEE
> > > card in MPC855 at 80/40 and HHL kernel 2.2.14 with PCMCIA-patch from
> > > Montavista and minor modifications for custom card.
> >
> > I am trying to get the wavelan card working as well. My setup is a
> > little different. 823e with 2.4.2 and pcmcia-cs-3.1.24. I got further
> > than you did. The card initialized fine and I can use ifconfig to
> > assign an IP address and bring the interface up. However as soon as I
> > try to transmit packets I get timeout error's. I have seen this
> > behavior on other wireless cards and it was due to timing. You probably
> > need to play with the timing that is setup in m8xx_pcmcia.c in
> > pcmcia-cs.
> >
> > let me know if you figure it out before i do.
> >
> > The Aironet4800B/Cisco340 and Prism chipset cards work fine. I did find
> > that the Aironet4800 won't work. I believe due to the timing settings
> > on the 8xx are incompatible with that card.
> >
> > >
> > > PC Card is found and wvlan_cs module installed, but the
> > > driver fails at initialization phase to timeout, presumably at
> > > hcfio_string-function. Other cards (for example serial_cs or 3c589
> > > seem to work). So, has anyone any ideas what could go wrong with this
> > > one?
> > >
> > > 1. IO-space is initialized to base 0x8100,size 0x3F and 16bit port
> > >size. (PBR5=0x8100, POR5=0x28024659)
> > >
> > > 2. Interrupts are handled, but none occurs during initialization (in
> > >other drivers interrupts however work).
> > >
> > > 3. Accesses to IO-space go to correct area, ie. 0x8100-0x813F.
> > >Writes to cards registers (for example at address 0x8128) seem
> > >to work, ie. I can write a word and read it back later.
> > >
> > > 4. config.opts includes "include port 0x100-0xfff" and "include memory
> > >0x8000-0x80ff".
> > >
> > > 5. How should the macros IN/OUT_PORT_WORD and IN/OUT_PORT_STRING in
> > >wvlan_hcfcfg.h be declared? I assume that as below, ie. all
> > >accesses non-swapping, or am i wrong? At least Lucent documentation
> > >says so...
> > >
> > > (http://bwrc.eecs.berkeley.edu/People/Grad_Students/jbeutel/wavelan_s0005-11-light.htm)
> > >
> > > 6. What else could go wrong?
> > >
> > > Best Regards,
> > > Janne Lintuala
> > >
> > > #define wvlan_inb(port) in_8((unsigned char
> > > *)((port)+_IO_BASE))
> > > #define wvlan_outb(val, port) out_8((unsigned char
> > > *)((port)+_IO_BASE), (val))
> > > #define wvlan_inw(port) in_be16((unsigned short
> > > *)((port)+_IO_BASE))
> > > #define wvlan_outw(val, port) out_be16((unsigned short
> > > *)((port)+_IO_BASE), (val))
> > > #define wvlan_insw(port, buf, ns) _insw_ns((unsigned short
> > > *)((port)+_IO_BASE), (buf), (ns))
> > > #define wvlan_outsw(port, buf, ns) _outsw_ns((unsigned short
> > > *)((port)+_IO_BASE), (buf), (ns))
> > >
> > > #define IN_PORT_BYTE(port) ((hcf_8)wvlan_inb((hcf_io)(port)))
> > > #define IN_PORT_WORD(port)
> > > ((hcf_16)wvlan_inw((hcf_io)(port)))
> > > #define IN_PORT_WORD_NO_DEBUG(port)
> > > ((hcf_16)wvlan_inw((hcf_io)(port)))
> > > #define OUT_PORT_BYTE(port, value) wvlan_outb((hcf_8)(value),
> > > (hcf_io)(port))
> > > #define OUT_PORT_WORD(port, value) wvlan_outw((hcf_16)(value),
> > > (hcf_io)(port))
> > > #define IN_PORT_STRING wvlan_insw
> > > #define OUT_PORT_STRING wvlan_outsw
> > >
> > > ---clip---
> > > Apr 2 18:27:41 hp-02 kern.info Linux PCMCIA Card Services 18:11:51 3.1.25
> > > Apr 2 18:27:41 hp-02 kern.info kernel bui
glibc-2.2.2
Magnus Damm wrote: > > Hi all, > > Anyone tried glibc-2.2.2? yep. we found it crashes in the dynamic loader on a cache instruction during a memset for loading the second dynamic library. since libc is always the first library loaded any application that only uses libc works. any app that uses more than libc, seg faults. > It cross-compiles cleanly, but acts wierd on my mpc8xx target. > > I've browsed through my old 2.1.3 patches for the cacheline- > size and I'm not sure if everything is ok with 2.2.2... > we are working it as I type. my guess is the cacheline patches didn't make it. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
MPC855 PCMCIA & wvlan_cs
Janne Lintuala wrote: > I's trying to use wvlan_cs (from pcmcia-cs-3.1.25) with Lucent/IEEE > card in MPC855 at 80/40 and HHL kernel 2.2.14 with PCMCIA-patch from > Montavista and minor modifications for custom card. I am trying to get the wavelan card working as well. My setup is a little different. 823e with 2.4.2 and pcmcia-cs-3.1.24. I got further than you did. The card initialized fine and I can use ifconfig to assign an IP address and bring the interface up. However as soon as I try to transmit packets I get timeout error's. I have seen this behavior on other wireless cards and it was due to timing. You probably need to play with the timing that is setup in m8xx_pcmcia.c in pcmcia-cs. let me know if you figure it out before i do. The Aironet4800B/Cisco340 and Prism chipset cards work fine. I did find that the Aironet4800 won't work. I believe due to the timing settings on the 8xx are incompatible with that card. > > PC Card is found and wvlan_cs module installed, but the > driver fails at initialization phase to timeout, presumably at > hcfio_string-function. Other cards (for example serial_cs or 3c589 > seem to work). So, has anyone any ideas what could go wrong with this > one? > > 1. IO-space is initialized to base 0x8100,size 0x3F and 16bit port >size. (PBR5=0x8100, POR5=0x28024659) > > 2. Interrupts are handled, but none occurs during initialization (in >other drivers interrupts however work). > > 3. Accesses to IO-space go to correct area, ie. 0x8100-0x813F. >Writes to cards registers (for example at address 0x8128) seem >to work, ie. I can write a word and read it back later. > > 4. config.opts includes "include port 0x100-0xfff" and "include memory >0x8000-0x80ff". > > 5. How should the macros IN/OUT_PORT_WORD and IN/OUT_PORT_STRING in >wvlan_hcfcfg.h be declared? I assume that as below, ie. all >accesses non-swapping, or am i wrong? At least Lucent documentation >says so... > > (http://bwrc.eecs.berkeley.edu/People/Grad_Students/jbeutel/wavelan_s0005-11-light.htm) > > 6. What else could go wrong? > > Best Regards, > Janne Lintuala > > #define wvlan_inb(port) in_8((unsigned char > *)((port)+_IO_BASE)) > #define wvlan_outb(val, port) out_8((unsigned char > *)((port)+_IO_BASE), (val)) > #define wvlan_inw(port) in_be16((unsigned short > *)((port)+_IO_BASE)) > #define wvlan_outw(val, port) out_be16((unsigned short > *)((port)+_IO_BASE), (val)) > #define wvlan_insw(port, buf, ns) _insw_ns((unsigned short > *)((port)+_IO_BASE), (buf), (ns)) > #define wvlan_outsw(port, buf, ns) _outsw_ns((unsigned short > *)((port)+_IO_BASE), (buf), (ns)) > > #define IN_PORT_BYTE(port) ((hcf_8)wvlan_inb((hcf_io)(port))) > #define IN_PORT_WORD(port) ((hcf_16)wvlan_inw((hcf_io)(port))) > #define IN_PORT_WORD_NO_DEBUG(port) ((hcf_16)wvlan_inw((hcf_io)(port))) > #define OUT_PORT_BYTE(port, value) wvlan_outb((hcf_8)(value), > (hcf_io)(port)) > #define OUT_PORT_WORD(port, value) wvlan_outw((hcf_16)(value), > (hcf_io)(port)) > #define IN_PORT_STRING wvlan_insw > #define OUT_PORT_STRING wvlan_outsw > > ---clip--- > Apr 2 18:27:41 hp-02 kern.info Linux PCMCIA Card Services 18:11:51 3.1.25 > Apr 2 18:27:41 hp-02 kern.info kernel build: 2.2.14 #979 Mon Apr 2 > 16:43:30 EEST 2001 > Apr 2 18:27:41 hp-02 kern.info options: none > Apr 2 18:27:41 hp-02 kern.debug cs.c 1.274 2001/03/05 04:01:49 (David Hinds) > Apr 2 18:27:42 hp-02 kern.info m8xx_pcmcia: Version 0.03, 14-Feb-2000, > Magnus Damm > Apr 2 18:27:42 hp-02 kern.debug cs: CardServices(GetCardServicesInfo, > 0xc0c87d88, 0x003c) > Apr 2 18:27:42 hp-02 kern.info m8xx_pcmcia: HP $Revision: 1.1 $ using SLOT_A > with IRQ 13. > Apr 2 18:27:42 hp-02 kern.debug m8xx_pcmcia: Socket 0: MemWin 0: Base > 0xe000. > Apr 2 18:27:42 hp-02 kern.debug m8xx_pcmcia: Socket 0: MemWin 1: Base > 0xe400. > Apr 2 18:27:42 hp-02 kern.debug m8xx_pcmcia: Socket 0: MemWin 2: Base > 0xe800. > Apr 2 18:27:42 hp-02 kern.debug m8xx_pcmcia: Socket 0: MemWin 3: Base > 0xec00. > Apr 2 18:27:42 hp-02 kern.debug m8xx_pcmcia: Socket 0: MemWin 4: Base > 0xf000. > Apr 2 18:27:42 hp-02 kern.debug cs: register_ss_entry(1, 0xc40141a0) > Apr 2 18:27:42 hp-02 kern.debug m8xx_pcmcia: Service(0, 4, 0xc0b8e808) > Apr 2 18:27:42 hp-02 kern.debug m8xx_pcmcia: SetSocket(0, flags 0x000, Vcc > 0, Vpp 0, io_irq 0, csc_mask 0x80) > Apr 2 18:27:42 hp-02 kern.debug m8xx_pcmcia: Service(0, 6, 0xc0c87d08) > Apr 2 18:27:42 hp-02 kern.debug m8xx_pcmcia: SetIOMap(0, 0, 0x00, 0 ns, > 0x-0x0001) > Apr 2 18:27:42 hp-02 kern.debug m8xx_pcmcia: Service(0, 6, 0xc0c87d08) > Apr 2 18:27:42 hp-02 kern.debug m8xx_pcmcia: SetIOMap(0, 1, 0x00, 0 ns, > 0x-0x0001) > Apr 2 18:27:42 hp-02 kern.debug m8xx_pcmcia: Service(0, 8, 0xc0c87cf8) > Apr 2 18:27:42 hp-02
NTSC Video on the 823
"Todd_Tomaino"@vnci.net wrote:
>
> Where did you find these files?
>
> ftp://ftp.mvista.com/pub/Area51/embedded-planet/video.tgz
oh yeah, I guess i put it there:-)
>
> Matthel Locke wrote:
> >>chuck's code is based on a different i2c driver than the one in
> >>8xx_io. Unless Todd has the i2c driver developed by EP, it probably
> >>won't work
>
> The "patchVideo" file contains an I2c driver. I did not load it, assuming
> that the more recent version I currently use would be preferable and
> compatible. I will try recompiling with the "patch Video" version and see
> if there is any change.
yep, that is the problem. the i2c driver in the kernel source doesn't
have write capablity. which is why the open (below) fails.
>
> >>>Where is this "Open error -19" coming from? There is lots more
> >>>code executed than your little snippet shows.
>
> It could be from this code segment located in Vid823.c, I'm not sure what
> this indicates.
>
> /* open or close a file in kernel space... */
> struct file *drvfopen(const char * filename, int flags, int mode)
> {
> struct file *f;
> int error;
>
> f = filp_open(filename, flags, mode);
> error = PTR_ERR(f);
> if (IS_ERR(f))
> {
> >printk("Open error %d\n",error);
> return 0;
> }
> return f;
>
> thanks for the help!
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
NTSC Video on the 823
chuck's code is based on a different i2c driver than the one in
8xx_io. Unless Todd has the i2c driver developed by EP, it probably
won't work
Dan Malek wrote:
>
> "Todd M. Tomaino" wrote:
>
> > I followed the readme instructions for adding the VideoTest.c and Vid823.c
> > files with the following header comments:
>
> Where did you find these files?
>
> > + * Started with Dan's LCD code, created NTSC Video Driver (4/2000)
> > + * Chuck Spaur (chuck at spaur.com)
>
> Although I wrote the first LCD driver, it has been fortunately discarded
> and written as a proper frame buffer driver by others (at least Joe
> Green). I have no idea what Chuck did to the original driver when
> he created this one.
>
> > made it to here !!!
> > Open error -19
>
> Where is this "Open error -19" coming from? There is lots more
> code executed than your little snippet shows.
>
> > void initVideo(IMAGEINFO *p_image)
> > {
> > int num_pages, i, j;
> > u_char *fbuf, *cp;
> > printf("made it to here !!!\n");
> > =>>>if ((p_image->display_fd = open("/dev/vid", O_RDWR)) < 0) {
> > perror("video open");
> > exit(2);
>
> Either your open is actually successful and further in the program
> there is some error, or the driver is failing in the open function
> and printing that error above. It looks like some NULL pointer
> dereference.
>
> -- Dan
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Problem implementing pcmcia_cs on ppc 823 hardware
Try upgrading to the latest pcmcia-cs which is 3.1.24. There have been several changes. Are you sure your card is 16 bit? Typically the 100Mbit cards are CardBus(32bit). David Hopcroft wrote: > > Hi, > > I wonder if any one can shed some light on a problem I am having? I am trying > to implement PCMCIA services on a custom PPC based board. > > I am using; > Processor - PPC 823 @ 64MHz > Kernel - 2.2.14 > Card Services - 3.1.10 > PCMCIA card - Xircom CreditCard Ethernet (CE3B-100BTX) > > I "insmod" the required modules (pcmcia_core, m8xx_pcmcia, ds and xirc2ps_cs) > and run cardmgr. > > The problem arises when I insert a pcmcia card, into it's slot. At which > point I get a "Kernel panic: machine check". This seems to be around the > area, > in the code, where the card services are starting to read it's CIS/attribute > area. > > I have iormap'd _IO_BASE to 0x8000 in init.c > > My BMT is enabled but set to 255(Max value). > > The bus frequency of the board is 32Mhz I have tried setting this in the code > to values of 32 & 3200 with the same results. looking at file > m8xx_pcmcia.c > it should be set to the latter. > > Can any one suggest any thing obvious I have missed, or misunderstood? > > I can post a debug log if required, but it's quite long. > > --- > David Hopcroft > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
[Question] init does not find library files.....
you are probably missing an important link. It is in .../target/opt/hardhat... Include that link in your ramdisk and it should work fine. kingseft at samsung.co.kr wrote: > > Thank for your kindful replying for our question about ramdisk. > > Now we installed HardHat Linux CDK and found file system in /targer > directory. > we follwed all procedures and made ramdisk.gz > > But, when we ran this ramdisk iamge, init didn't found libc.so.6 > of course, we put this libc.so.6 file into our /lib directory in ramdisk.gz > following is our result... > > We need your comments, any comments will help us.. thanks... > > --- our experiment result -- > > RAM disk driver initialized: 16 RAM disks of 10240K size > loop: registered device at major 7 > eth0: CPM ENET Version 0.2, 00:05:27:00:00:01 > RAMDISK: Compressed image found at block 0 > EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended > VFS: Mounted root (ext2 filesystem). > Freeing unused kernel memory: 28k in > init: error in loading shared libraries: libc.so.6: cannot open shared object > fi > le: No such file or directory <--- Here is our problem!!! > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Status of linux-ppc kernel.
Subodh Nijsure wrote: > > Also there seem to be few patches like Wolfgang's ethernet patch > found on ftp.denx.de or m8xx_pcmcia stuff that hasn't shown up in > 2.4.X latest kernel. Are these things going to get merged into > "mainline" sometime and does anybody know probable dates etc.? m8xx_pcmcia is a part of the pcmcia-cs tree. The kernel changes depend on where you ioremap memory for pcmcia, which is board dependent. I need to send Dan a kernel patch for the EP boards, but I haven't done it yet:( ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Getting SanDisk CompactDisk working on linux-ppc.
Subodh Nijsure wrote: > > I got m8xx_pcmcia.c to "work" with Linux version 2.4.2-pre3 that > I got from bitkeeper. what do mean by "work"? did you need to make changes to m8xx_pcmcia for 2.4? > When I say m8xx_pcmcia works, cardctl ident shows it as > a Sandisk device in socket 0, and dump_cis show me attached info. that is fine. > What I would like to do is mount this device as ide drive, can anybody > wants to provide pointers to how I can do this? It already is an ide drive. In order to mount it, you must put a filesystem on it. If you kept the orginal scripts for pcmica-cs, then the SanDisk is /dev/hde. the cardmgr should write that info out to the console or log file. > /Subodh Nijsure > > --- > sh-2.04# cardctl ident > Socket 0: > product info: "SunDisk", "SDP", "5/3 0.6" > manfid: 0x0045, 0x0401 > function: 4 (fixed disk) > sh-2.04# cardctl status > Socket 0: > 5V 16-bit PC Card > function 0: [ready], [bat dead], [bat low] > --- > sh-2.04# dump_cis | more > Socket 0: > dev_info > fn_specific 700ns, 2kb > common_jedec 0xdf 0x01 > manfid 0x0045, 0x0401 > vers_1 4.1, "SunDisk", "SDP", "5/3 0.6" > funcid fixed_disk [post] > disk_interface [ide] > disk_features [silicon] [unique] [single] > [sleep] [standby] [idle] [low power] > config base 0x0200 mask 0x000f last_index 0x07 > cftable_entry 0x00 [default] > [rdybsy] [mwait] [pwrdown] > Vcc Vnom 5V Vmin 4500mV Vmax 5500mV Ipeak 80mA > memory 0x-0x07ff @ 0x > cftable_entry 0x00 > Vcc Vnom 3300mV Ipeak 45mA > cftable_entry 0x01 [default] > [rdybsy] [pwrdown] > Vcc Vnom 5V Vmin 4500mV Vmax 5500mV Ipeak 80mA > io 0x-0x000f [lines=4] [8bit] [16bit] > irq mask 0x [level] [pulse] [shared] > cftable_entry 0x01 > Vcc Vnom 3300mV Ipeak 45mA > cftable_entry 0x02 [default] > [rdybsy] [pwrdown] > Vcc Vnom 5V Vmin 4500mV Vmax 5500mV Ipeak 80mA > io 0x01f0-0x01f7, 0x03f6-0x03f7 [lines=10] [8bit] [16bit] [range] > irq 14 [level] [pulse] [shared] > cftable_entry 0x02 > Vcc Vnom 3300mV Ipeak 45mA > cftable_entry 0x03 [default] > [rdybsy] [pwrdown] > Vcc Vnom 5V Vmin 4500mV Vmax 5500mV Ipeak 80mA > io 0x0170-0x0177, 0x0376-0x0377 [lines=10] [8bit] [16bit] [range] > irq 14 [level] [pulse] [shared] > cftable_entry 0x03 > Vcc Vnom 3300mV Ipeak 45mA > cftable_entry 0x07 > -- > sh-2.04# cat /proc/interrupts >CPU0 > 1: 0 8xx SIU Edge cxe > 2: 0 8xx SIU Edge mii > 3:481 8xx SIU Edge fec > 5: 11711 8xx SIU Edge cpm > 13: 0 8xx SIU Edge m8xx_pcmcia > 15: 0 8xx SIU Edge tbint > BAD: 0 > --- > > sh-2.04# cat /proc/devices > Character devices: > 1 mem > 2 pty > 3 ttyp > 4 ttyS > 5 cua > 10 misc > 89 i2c > 90 mtd > 162 raw > 254 pcmcia > > Block devices: > 1 ramdisk > 31 mtdblock > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
linux kernel patch for Motorola FADS
Kirk Lee wrote: > And how to get the Area51 of Montavista server?? > I do not find a link pointing to Area51 yet!! ftp://ftp.mvista.com/pub/Area51 ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RPX Lite w MontaVista 1.2
no that works too. The old bootloader (RPX-Utility) always setup the BR/OR for NVRAM even if the board did not have NVRAM populated. In the new bootloader NVRAM is not mapped by default. if you enable NVRAM in its config it will setup the BR/OR and then the kernel can access that area of memory. Obviously, if you acutally try to do something with that area... --Original Message-- From: Dan Malek <[EMAIL PROTECTED]> To: Brett Carswell Sent: December 18, 2000 3:02:12 AM GMT Subject: Re: RPX Lite w MontaVista 1.2 Brett Carswell wrote: > > I enabled the NVRAM in the config and everything works great now. That's weird. Something else is wrong. The NVRAM config is irrelevant on the RPX-lite (and I think all 8xx boards). The code I suggested you remove is run long before the kernel, and the information you sent earlier indicated the actual NVRAM was not mapped in the memory controller. -- Dan _ OneMain.com, Your Hometown Internet. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PCMCIA Card Service
you need to install the kernel patches on the ftp site as well. the patch with ide and kernel in the name take care of that problem. Nguyen Xuan Hoang wrote: > > Hi Matthew, > > Thank very much for your info. I have look at your patch but it seems not > solving our problem. I would like explain more: > > - From my investigation is: there's one confliction of the interrupt: > > 1. The PCMCIA card service (m8xx_pcmcia) register it's interrupt handler by > calling: > request_8xxirq(pcmcia_schlvl, m8xx_interrupt, 0, "m8xx_pcmcia", NULL); >well, that seems logical. > > 2. But when an PCMCIA card plug in, it remap the memory and route it's > interrupt to the system interrupt (of course only one PCMCIA interrupt). The > problem is most of driver using REQUEST_8XXIRQ to register the handler. For > Example the FLASH card will call IDE driver, IDE driver will call > IDE_REQUEST_IRQ to register ide_intr. > As I saw the IDE_REQUEST_IRQ call REQUEST_8XXIRQ with PCMCIA interrupt. It > fails because the interrupt already occupy by PCMCIA (see step 1). > > I may be wrong...please give me some advices > > Thank in advances. > Hoang > > > > > yeah, I have done it. use my patches on > > ftp://ftp.mvista.com/pub/Area51/ppc_8xx. I still have not done a > > README, but if you have a MV support contract just contact support and > > they will help you out. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PCMCIA Card Service
Nguyen Xuan Hoang wrote: > > Hi, > > I'm trying to get the PCMCIA CardService running on an mpc823 board > (RPX Lite). I pick up the code from Jo-Ellen Mathews of AbsoluteValue > Systems,and I can do something like remap memory, read data from IO > port...But end up with IRQ probe fail (I start with PCMCIA Flash Card). I > did an investigating and find out the reason, that is PCMCIA card service > already occupy the PCMCIA interrupt and I can not use request_8xxirq to > register another handler . > > I am thinking that I may have to rewrite request_8xxirq and pcmcia interrupt > handler to solve this case. Is there any better solution? Have any one have > done it? I am very appreciated for any help. yeah, I have done it. use my patches on ftp://ftp.mvista.com/pub/Area51/ppc_8xx. I still have not done a README, but if you have a MV support contract just contact support and they will help you out. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
[linuxppc-embedded] PCMCIA on MBX860
strange, I haven't seen that before. check the BCSRs. Perhaps a difference between the MBX and EP boards was missed, and it is turning off the ethernet transmit? That is my guess. "Ruhland, Paul" wrote: > > > you need to change a config file. > > > > in /etc/sysconfig/pcmcia > > > > change the i82365 to m8xx_pcmica > > > Ahhh...that was it. Now, when the pcmcia stuff is starting up I lose my > eth0 nfs connection... > > --- > sh-2.03# /t etc/init.d/pcmcia start > Starting PCMCIA services: modulesLinux PCMCIA Card Services 3.1.19 > kernel build: 2.2.14 #10 Tue Nov 21 11:37:36 GMT-5 2000 > options: none > m8xx_pcmcia: Version 0.03, 14-Feb-2000, Magnus Damm > m8xx_pcmcia: MBX860 using SLOT_A with IRQ 13. > nfs: server 10.2.129.62 not responding, still trying > eth0: transmit timed out. > Ring data dump: cur_tx fa202958 (full) cur_rx fa202930. > 9c00 0096 00153c82 > 9c00 0096 001535c2 > 9c00 0096 001536e2 > 9c00 0096 001534a2 > 9c00 0096 00153802 > 9c00 0096 00153922 > 9c00 0096 00153a42 > bc00 0096 00153b62 > 9c00 05ee 001ee000 > 9c00 0362 001ee800 > 9c00 05ee 001ed000 > 9c00 05ee 001ed800 > 9c00 00ae 001ec000 > 9c00 00ae 001ec800 > 9c00 0502 001eb000 > bc00 05ee 001eb800 > eth0: tx queue full!. > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
[linuxppc-embedded] PCMCIA on MBX860
you need to change a config file. in /etc/sysconfig/pcmcia change the i82365 to m8xx_pcmica "Ruhland, Paul" wrote: > > Matthew, > > I used 'pcmcia-cs-3.1.19.tar.gz', 'hhl-8xx_pcmcia-3.1.19.patch', and > 'hhl-8xx-kernel_pcmcia.patch' from the mvista site. > > After adding MBX board specific code to 'modules/m8xx_pcmcia.c' the package > succesfully compiles. However, I now get the following errors when I try to > load the module(s): > > > sh-2.03# /etc/init.d/pcmcia start > Starting PCMCIA services: modulesLinux PCMCIA Card Services 3.1.19 > kernel build: 2.2.14 #10 Tue Nov 21 11:37:36 GMT-5 2000 > options: none > /lib/modules/2.2.14/pcmcia/i82365.o: /lib/modules/2.2.14/pcmcia/i82365.o: No > suyds: no socket drivers loaded! > /lib/modules/2.2.14/pcmcia/ds.o: init_module: Device or resource busy > cardmgr. > cardmgr[74]: starting, version is 3.1.19 > sh-2.03# cardmgr[74]: no pcmcia driver in /proc/devices > cardmgr[74]: exiting > > sh-2.03# lsmod > Module Size Used by > pcmcia_core38032 0 > sh-2.03# > - > I was under the impression from your previous post that the socket driver > was part of the patch...am I mistaken? If it is...I assume I must load it > first...what is it called? ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
init problems with 2.4.0 kernel
t.shantha.laxmi at exgate.tek.com wrote: > It is a ppc board running linux kernel 2.4.0-test2-1.2.2-1. I have > downloaded the kernel from the mvista site. I am using CDK1.0(again got from > mvista) as the root filesystem. With my earlier version of the kernel > (2.2.13), I was not facing this problem. > > Any help will be greatly appreciated, > - Shantha > First let me say that 2.4 is still considered an unstable kernel. Montavista only supports the 2.4 kernel for a couple of arch that are only in 2.4. If you are looking to upgrade your kernel for a product release, stick with 2.2.14. otherwise, always use the latest 2.4 kernel and expect something to be broken. Matthew Locke Montavista Software ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
[linuxppc-embedded] PCMCIA on MBX860
I have pcmcia-cs working on the Embedded Planet boards, but I haven't tested on a MBX. I assume that the MBX uses the builtin pcmcia controller on the 8xx. if that is the case, then you need the 8xx socket driver. It is included with the card services package starting with verison 3.1.23. Also I have patches on ftp://ftp.mvista.com/Area51/ppc_8xx. If changes are needed for the MBX, let me know and I will get them into the 8xx socket driver. "Ruhland, Paul" wrote: > > I've had zero success compiling the pcmcia-cs-3.1.19 card services package > for an MBX860 board. > > Using: > mVista hardhat kernel 2.2.14 > mVista hardhat cross compiler > > Its choking in 'modules/i82365.c' with the following error: > > #error "no bus architectures defined!" > > From this, I figured I needed to include either PCI or ISA support in my > kernel config. However, enabling QSpan PCI in kernel configuration yields > errors during kernel build. > > Has anyone gotten the card services to work on an MBX board? > > -- > Paul Ruhland > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Warning: unable to open an initial console.
> Any ideas? I took a look at the /opt/hardhat/devkit/ppc/8xx/target > directory, I can find a "dev" directory but there is nothing in it. Is > there some RPM I need to install? I think that I have > downloaded/installed all of the RPM's from the mvista ftp site. > either you missed an RPM or you were not root when you installed. try installing the filesystem RPM again. Matthew Locke Montavista Software ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PCMCIA Problems
I set _IO_BASE to 0x8000 and it worked fine in 2.2.14. My patches are on our ftp site. ftp://ftp.mvista.com/Area51/ppc_8xx clark at esteem.com wrote: > > Hello, > > I seem to be having trouble with getting pcmcia-cs working. I am > using a > custom board with a MPC850 running PPCBoot and HardHat Linux. Everything > seems to work fine up until Cardmgr loads. I know I need to define _IO_BASE > and its size but I'm not sure how to figure out what to set it to. I have > tried to set it to various values 0x8000, 0xEC00, 0xC000, and > 0xD000 all with no luck. Do I need to do more than declare it? > > here is typical output. > > Hit any key to stop autoboot: 0 > ## Booting Linux kernel at 4003 ... > Image Name: 2.2.13 for EST192E > Image Type: PowerPC Linux Kernel Image (gzip compressed) > Data Size:412481 Bytes = 402 kB = 0 MB > Load Address: > Entry Point: 000c > Verifying Checksum ... OK > Uncompressing Kernel Image ... OK > Linux version 2.2.13 (brent at strecker.esteem.com) (gcc version 2.95.2 > 19991024 > (release)) #20 Fri Oct 27 09:53:01 PDT 2000 > Boot arguments: root=/dev/nfs rw ip=100.100.100.21:100.100.100.11:100.100.100. > 1:255.0.0.0:esteem192e.com:eth0 nfsroot=100.100.100.11:/home/brent/dk80211b/ro > otfs.nfs > time_init: decrementer frequency = 18375/60 > Calibrating delay loop... 48.84 BogoMIPS > Memory: 15132k available (748k kernel code, 464k data, 40k init) [c000,c10 > 0] > DENTRY hash table entries: 262144 (order: 9, 2097152 bytes) > Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes) > Page-cache hash table entries: 4096 (order: 2, 16384 bytes) > POSIX conformance testing by UNIFIX > Linux NET4.0 for Linux 2.2 > Based upon Swansea University Computer Society NET3.039 > NET4: Unix domain sockets 1.0 for Linux NET4.0. > NET4: Linux TCP/IP 1.0 for NET4.0 > IP Protocols: ICMP, UDP, TCP, IGMP > TCP: Hash tables configured (ehash 16384 bhash 16384) > Starting kswapd v 1.1.1.1 > CPM UART driver version 0.03 > ttyS00 at 0x0280 is a SMC > ttyS01 at 0x0380 is a SMC > pty: 256 Unix98 ptys configured > RAM disk driver initialized: 16 RAM disks of 4096K size > loop: registered device at major 7 > NET4: Ethernet Bridge 008 for NET4.0 > eth0: CPM ENET Version 0.2, 00:00:00:00:00:00 > PPP: version 2.3.7 (demand dialling) > TCP compression code copyright 1989 Regents of the University of California > PPP line discipline registered. > Looking up port of RPC 13/2 on 100.100.100.11 > Looking up port of RPC 15/1 on 100.100.100.11 > VFS: Mounted root (NFS filesystem). > Freeing unused kernel memory: 40k init > INIT: version 2.77 booti > Linux PCMCIA Card Services 3.1.10 >kernel build: 2.2.13 #20 Fri Oct 27 09:53:01 PDT 2000 >options: none > m8xx_pcmcia: Version 0.03, 14-Feb-2000, Magnus Damm > m8xx_pcmcia: ESTEEM192E using SLOT_B with IRQ 13. > p80211.o: 0.1.7 Loaded > cardmgr[17]: starting, version is 3.1.10 > cardmgr[17]: watching 1 sockets > cardmgr[17]: initializing socket 0 > Machine check in kernel mode. > Caused by (from msr): regs c0c75850 Unknown values in msr > NIP: C4003C94 XER: C000FF7F LR: C4003C70 REGS: c0c75850 TRAP: 0200 > MSR: 9032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 > TASK = c0c74000[17] 'cardmgr' mm->pgd c0c7f000 Last syscall: 54 > last math > GPR00: C4016000 C0C75900 C0C74000 C4015000 C0C09054 01F7 C00D3000 0015 > > GPR08: 0C40 C4015000 C0C123AC 1000 35F33F34 10021500 1009FFD0 > > GPR16: 100A6310 00FBFE38 9032 00C75E80 C0002544 > > GPR24: C0002284 0002 C00E886C C0C7596A 0002 C00E8800 C4015000 > > Call backtrace: > C4003C70 C4004418 C4004978 C4004700 C400608C C40038C8 C400F4C8 > C0032FC4 C00022D8 100018A0 10002A50 10003FF0 0FF09E78 > > Kernel panic: machine check > Rebooting in 180 seconds.. > > With a silly scope I can see the pcmcia device assert the RDY/BSY_B > line > after it is reset, and /CE1_B & /CE2_B get asserted once just before it > explodes in my face. > > Any help apprieciated, Many thanks in advance. > > Conn > * >If you live at home long enough, your parrents will move out. > * > > Conn Clark > Engineering Stooge clark at esteem.com > Electronic Systems Technology Inc. www.esteem.com > > Stock Ticker Symbol ELST > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
pointers to ld.so.1
Ralph Blach wrote: > > I am working the Monta Vista port of linux to the IBM405gp > and I am trying to put in a ramdisk. What links do i need in a ramdisk > so that > the libraries can be found. Right now, I get the message > > initKernel panic: Attempted to kill init! > : error in loading shared libraries: libdl.so.2:Rebooting in 180 > seconds.. cannot open shared object file: No such file or directory > > Yet libdl.so.2 and all the links are the the /lib directory. > you are probably missing the link on the target /opt/hardhat/devkit/ppc/4xx/powerpc-hardhat-linux -> / ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PCMCIA - another step...
Paolo Scaffardi wrote: I have some patches for the kernel and pcmcia-cs for the 8xx on our ftp site. ftp://ftp.mvista.com/pub/area51/ppc_8xx I moved Magnus stuff up to pcmcia-cs-3.1.19 and there is a patch for the ioremapping of _IO_BASE. I chose 0x8000 but that probably is not the best place to put it. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Ethernet Trouble
clark at esteem.com wrote: > Sending BOOTP and RARP requests. timed out! > IP-Config: Auto-configuration of network failed. > dev_close: bug eth0 still running > Looking up port of RPC 13/2 on 100.100.100.14 > RPC: sendmsg returned error 101 > RPC: sendmsg returned error 101 > looks like a config problem. trying turning off RARP in the kernel. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
823e LCD display - Microwindows
jonb at marel.is wrote: > > Hi > > I have now successfully gotten Linux running on a custom 823e board, > using Monta Vista CDK 1.2, Linux version 2.2.14. I am using an NFS > root file system and I have created a custom lsp for the board. > > Our board uses the 823 LCD controller for a 640x480 TFT display. > > I would like to activate the 823 LCD driver and try out the Microwindows > demo from Monta Vista, but I do not know what needs to be done. > > When I configure the kernel with CONFIG_RPXLCD, I get a lot of > undefined symbols when linking the kernel, such as fb_display, > fb_default_cmap. > > Can anyone point me in the right direction ? Enable framebuffer support in the kernel configuration. Matthew Locke Montavista Software ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Using both (the 10Mbps and 100 Mbps) ports on CLLF 860T with Hard Hat Linux
rshaw at graftononline.net wrote: > > I'm using a CLLF 860T with Embedded PowerPC Cross Development Kit Rev. 1.2 > Hard Hat Linux. I'm very new to Linux and developing for a board. Currently, > I'm booting manually (loading the kernel with tftp) using the 10 Mbps > ethernet port. > I had to configure the kernel to use SCC1 so the 10 Mbps line > is used during the BOOTP requests. Everything you need to run on a cllf is enabled in the cllf kernel lsp. I suggest starting from the cllf lsp and then add/change kernel configuration options as needed. > > From the prompt in minicom I can make the cllf board ping my pc and from my > pc I can ping the cllf board, and this is using the 10 Mbps line. I will > also need to use the 100 Mbps line except I don't know if its possible to > use both ethernet ports and how to do it. of course it is possible. There are many different ways to do this. I am not sure what you need but here is one way. Simply use the cllf lsp, which already has both ethernet ports enabled and auto configure with bootp enabled. Then put the ethernet addresses for both ports in your dhcpd.conf with different ip's and only one with the root-path option. > Even if I could find a way to > switch between these ports, using only one port at a time, I would be happy. > Surely this is possible because the 10 Mbps port and 100 Mbps port have > different MAC addresses. you can do this as well. just enable the port you want in the kernel configuration and disable the one you do not want. Matthew Locke Montavista Software ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
CLLF with Hard Hat Lunix "Sending BOOTP requests" problem
rshaw at graftononline.net wrote: > > I'm trying to get a CLLF 860T to load a kernel normally. I'm using Embedded > PowerPC Cross Development Kit Rev. 1.0 Hard Hat Linux. you might want to upgrade to 1.2. it is on our ftp site. It is not nescessary, but it is always good to use the latest stable stuff. > While loading the kernel via tftp I found that in order for the boot process > to work I have to use both the 10 Mbps and 100 Mbps ports. the EP boot loader uses the 10Mbps port for tftp loading. You don't use the 10/100 for tftp. >If I do not do > this it times out at "Sending BOOTP requests". I have had to execute the > following script before loading via tftp during which time the 10 Mbps port > is being used. you only need to use the 10Mbps port, you don't need the 100Mbps port connected to the network. > > #!/bin/bash > arp -s 192.168.0.3 00:10:ec:00:00:00 that ethernet address is wrong. This may be causing some of your problems. Contact Embedded Planet support for help to reprogram the correct enet address for your board > OK, This gets us to a Linux shell prompt even though I had to execute the > script files using both the 10 Mbps and 100 Mbps ports, which I shouldn't > have to do. I'm hoping someone might be able to help me with why I need to > use both ports and execute these arp commands. Is something wrong with my > DHCP configuration? look into changing the enet address to the right one. the configuration looks fine. I hope the w2k host is not really running win2k. If it is, all bets are off. > Here is the /etc/hosts file contents > > 127.0.0.1 localhost.localdomain localhost > 192.168.0.1 win2000 w2k > 192.168.0.2 RANDYLINUX rlx > 192.168.0.3 CLLFBOARD cllf > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PPC cross compiled dhcpd doesn't work.
> Does any one succeeded in compiling and running dhcpd ? > My dhcpd is from http://www.isc.org/products/DHCP/ and ftp site > ftp://ftp.isc.org/isc/dhcp/dhcp-2.0pl4.tar.gz yes I have compiled and used it successfully on 8xx. Also I believe we provide ppc binaries in CDK 1.2 Matthew Locke Montavista Software http://www.mvista.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Problems building cross environment.
> So I want to know, are there anyone who build cross environment? > If you built cross environment before please tell me. > And if it's possible, please tell me what sources you use and > how can you build - what options? ,modify sources? Montavista has built a Cross Development Kit for several hosts to even more targets. Our sources and binaries are at ftp://ftp.mvista.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RPX Lite programming
Dan Winkler wrote: > > Newbie alert!!! I've just started developing on the > RPX lite board from embedded-planet. I am currently > trying to write some i2c code that just reads the > temperature registers from the temperature sensor and > thermal monitor (TCN75). I was wondering where > someone like myself could find some example code to > get me started. I found the i2c driver from the there is already a i2c driver for the 8xx in the kernel. It only has read capabilities, but it works fine (at least for reading the eeprom). There are several drivers for the 8xx in the kernel that you can use for examples. Also EP wrote a different i2c driver with write. the EP i2c driver has not made it to our ftp site yet, so ask EP tech support for it. Matthew Locke Montavista Software http://www.mvista.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Small JVM
prashant wrote: > > Hello everyone >I want to use JVM with MPC823 and linux. Can anybody suggest any small > JVM available in market ? > We at Montavista have several JVM solutions for HardHat Linux. In fact we just demoed some cool Java stuff at Linux World. Check out our web-site http://www.mvista.com for more info and contact info. Matthew Locke Montavista Software http://www.mvista.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Porting X to PowerPC platform
Paolo Scaffardi wrote: > > I am writing a framebuffer device for my MPC823FADS platform, and i need to > port a simple X-server based on the framebuffer to my PowerPC. nothing in X is ever simple :-) > > I looked at the XFree86 sources but it's not clear hot to compile them for > PowerPC targets! I guess size is not important for you. We (Montavista) are supporting Microwindows, which is a small footprint open-source windowing system for embedded systems (I must have said this a thousand times at LinuxWorld). you can find a srpm and a rpm for 8xx on our ftp site ftp://ftp.mvista.com. It is very light weight, but has several widgets (listbox, buttons, etc). > Are you already done this? > How can i proceed? > > I'm in a hurry... please help me soon! > yeah, if you are in a hurry, I suggest trying microwindows. It has both a Win323 API and a "X like" API into its graphics engine. If you are familiar with either one, you can have a simple app running in no time. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
I2C,SPI and QMC
Frank Przybylski wrote: > > Hi all, > I plan to use QMC on SCC1 plus SPI on a MPC855T / 860DT for an ISDN BRI > implementation. I also need I2C for other purposes. > Following the QMCSUPPLEMENT/AD manual from Motorola I found that one looses > either I2C using SCC1 for QMC/Ethernet or SPI using SCC2 for QMC/Ethernet. > I hoped that the I2C/SPI micro code patch would do the trick. But scanning > this > mailing list archive I got aware of troubles with this, or even worse that the > patch has been removed from the kernel. > So my question goes like this: > has anybody managed to use I2C, SPI and QMC on SCC1 altogether, or am I lost > without any hope? > I have successfully used SPI with ethernet on SCC2 with the microcode patch. However, I did that on a 823, I haven't tried it on the 855/860. I think I have used the i2c driver with the microcode patch on a 860, but don't quote me. This was all on the Embedded Planet boards. Matthew Locke Montavista Software http://www.mvista.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Usb slave API
> > From my understanding the usb slave driver (not host) was done for MPC823 > > and MPC850, but I can't find where it is As Dan said, hopefully the annoucement will happen soon. > > nor what is the API for it (In > > official linux kernel there's a API for USB host function). Am I right or > > too stupid? I hope some people in this maillist can give a point. Which kernel are you looking in? USB support in the 2.2 kernel isn't very stable. 2.4 has a very nice implementation and I think you can find backports to the 2.2. However backports are not always stable. Basically the kernel provides slave (peripheral) drivers for the basic peripheral classes, printer, scanner, mouse, keyboard, etc. look in drivers/usb for those files to use as examples. The first place to look is in the Documentation directory of the kernel tree. At the very least it will have pointers to where to find docs. In this case (2.4), it provides some good descriptions of the USB API and the various pieces that make up the USB stack. I read a paper called "Programming Guide for Linux USB Devices" that is pretty good. you can find it at http://usb.in.tum.de/usbdoc . Matthew Locke Montavista Software http://www.mvista.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
FWD: Installing PCMCIA hard disk on DVK MPC823
> My name's Phuc Le. I am new on this field. I just installed > PCMCIA HDD on the the DVK MPC823 but it failed. What is the DVK 823? I haven't heard of that one. > The result was the cardmgr detects the flugged pcmcia device to be > ATA/IDE and it tried to load the 'ide_cs.o' module. But it failed. The error > message were displayed as below: > > ide_cs.o: unresolved symbol 'ide_register' > ide_cs.o: unresolved symbol 'ide_unregister' > > I tried to rebuilt the kernel with turn-on some IDE features in the > configuration phase and recompile the pcmcia based on the new kernel. > > The result was still failed with the kernel to be panic status. > As usual Dan beat me to a response, but I can give a little more detail:-) My next task (probably after LinuxWorld this month) is to figure out all the details for making card services work on 8xx and document them. In the mean time, here is what I know: The 8xx portion of the kernel has some code that connects the PCMCIA controller to the IDE driver (without card services). this code is activated when you select the *_IDE and *_IDEDISK config options. So it probably is conflicting with the ide_cs modules in card services. I think if you pass in the ide=noprobe (check docs for exact args) at the boot prompt it might work, maybe. If you don't need hot swap, I suggest not using card services until I have packaged it for HardHat. Instead use the existing code that connects the controller to the IDE driver. You may need to tune some timing parameters to your PCMCIA h/w. I have a patch that makes it work with a SanDisk at ftp://ftp.mvista.com/pub/Area51/embedded-planet To do this: apply the patch Enable the _IDE and _IDEDISK kernel config options make dep; make zImage insert PCMCIA card load and boot linux I will post a message when Card Services is available on Montavista's ftp site. Matthew Locke Software Engineer Montavista Software ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
making kernel for ppc405gp from montavista sources
I believe 'make mrproper' blows away .config and autoconf.h. I don't know what the state of your tree is now, but try to copy the .config again "make 'your favorite config process'" (mine is xconfig) keep all defaults and 'save and exit'. this will create things like autoconf.h "make dep" "make 'your favorite image'" > -Original Message- > From: owner-linuxppc-embedded at lists.linuxppc.org > [mailto:owner-linuxppc-embedded at lists.linuxppc.org]On Behalf Of Matthias > Fuchs > Sent: Saturday, August 05, 2000 9:02 AM > To: linuxppc-embedded > Subject: making kernel for ppc405gp from montavista sources > > > > Hello, > > I downloaded the linux_tar.gz file from montavista and unpacked it ! I > copied the .config file from the same location to the kernel tree's > root. Before I did a "make mrproper". > > When I run a "make dep" I got an error ! Well, I could start to check > out if there is an error in the tree, but I think that there is a > general mistake I made ! > > Does anybody know where the error comes from ? Here is the output of my > "make dep": > > -- > mfuchs at pc-matthias:~/mvista_405_linux_new/linux > make dep > make -C arch/ppc/boot fastdep > make[1]: Entering directory > `/home/mfuchs/mvista_405_linux_new/linux/arch/ppc/boot' > /home/mfuchs/mvista_405_linux_new/linux/scripts/mkdep *.[Sch] > .depend > make[1]: Leaving directory > `/home/mfuchs/mvista_405_linux_new/linux/arch/ppc/boot' > make -C arch/ppc/chrpboot fastdep > make[1]: Entering directory > `/home/mfuchs/mvista_405_linux_new/linux/arch/ppc/chrpboot' > /home/mfuchs/mvista_405_linux_new/linux/scripts/mkdep *.[Sch] > .depend > make[1]: Leaving directory > `/home/mfuchs/mvista_405_linux_new/linux/arch/ppc/chrpboot' > make -C arch/ppc/treeboot fastdep > make[1]: Entering directory > `/home/mfuchs/mvista_405_linux_new/linux/arch/ppc/treeboot' > /home/mfuchs/mvista_405_linux_new/linux/scripts/mkdep *.[Sch] > .depend > make[1]: Leaving directory > `/home/mfuchs/mvista_405_linux_new/linux/arch/ppc/treeboot' > scripts/mkdep init/*.c > .depend > scripts/mkdep `find /home/mfuchs/mvista_405_linux_new/linux/include/asm > /home/mfuchs/mvista_405_linux_new/linux/include/linux > /home/mfuchs/mvista_405_linux_new/linux/include/scsi > /home/mfuchs/mvista_405_linux_new/linux/include/net -follow -name \*.h ! > -name modversions.h -print` > .hdepend > make _sfdep_kernel _sfdep_drivers _sfdep_mm _sfdep_fs _sfdep_net > _sfdep_ipc _sfdep_lib _sfdep_arch/ppc/kernel _sfdep_arch/ppc/mm > _sfdep_arch/ppc/lib _FASTDEP_ALL_SUB_DIRS="kernel drivers mm fs net ipc > lib arch/ppc/kernel arch/ppc/mm arch/ppc/lib" > make[1]: Entering directory `/home/mfuchs/mvista_405_linux_new/linux' > make -C kernel fastdep > make[2]: Entering directory > `/home/mfuchs/mvista_405_linux_new/linux/kernel' > make[2]: *** No rule to make target > `/home/mfuchs/mvista_405_linux_new/linux/include/linux/autoconf.h', > needed > by > `/home/mfuchs/mvista_405_linux_new/linux/include/linux/modules/sig > nal.ver'. > Stop. > make[2]: Leaving directory > `/home/mfuchs/mvista_405_linux_new/linux/kernel' > make[1]: *** [_sfdep_kernel] Error 2 > make[1]: Leaving directory `/home/mfuchs/mvista_405_linux_new/linux' > make: *** [dep-files] Error 2 > mfuchs at pc-matthias:~/mvista_405_linux_new/linux > > -- > > thanks for advise > Matthias > > -- > - > \ Matthias Fuchs \ > \ esd electronic system design Gmbh \ > \ Vahrenwalder Stra?e 205\ >\ D-30165 Hannover \ > \ email: matthias.fuchs at esd-electronics.com \ > \ phone: +49-511-37298-0 \ > \ fax: +49-511-37298-68\ >-- > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PCMCIA (some answers)
Well, at least one answer. There have been several people asking about using an ATA flash card with a RPX-lite. The kernel has some routines that connect the 8xx PCMCIA controller to the kernel's IDE driver. Two changes were necessary to make that work. One change is timing related specific to a SanDisk. I tested the patch on both a RPX-lite CW and a CLLF BW. Here are the steps I took to make this work apply patch ftp://ftp.mvista.com/pub/unsupported/embedded-planet/ select _IDE and _IDEDISK config options make dep make zImage Make sure you insert the flash card before you boot linux. the IDE driver probes for a disk at boot time. As for the pcmcia-cs questions... Magnus provided a patch to pcmcia-cs to run on 8xx and Jo-Ellen provided a kernel patch to the MV 2.2.13 kernel. Since Mark and Jo-Ellen wrote thier own pcmcia module (for thier super cool wireless project), they didn't run into the problems using the ide,ethernet pcmcia modules. I know that the above mentioned 8xx pcmcia/ide kernel routines conflict with the pcmcia-cs ide module. Some work in the kernel will be necessary to resolve that conflict. As for the ethernet problems, I tried several different 3COM models with strange results. I haven't looked into that any further. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Board recommendation?
> Would anyone care to recommend a board for testing/prototyping? > I was looking at the BrightStar ip-Engine and Embededded Planet > RPXLite but they only support the 823. EP supports the entire 8xx family in a variety of form factors. The 860 boards are called Classic, CLLF, LICC... ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
rpx_cfg() copy to NVRAM?
> I'm in the process of changing head.S and embed_config.c to work with the > new EP bootloader. Why? You don't need to change anything. There are two configuration variables in the eeprom that need to be set. SYPCR needs to be set to turn the watchdog off. Can't remember the value and I don't have the docs in front of me. NVRAM needs to be set to non-zero, even if the board doesn't have any nvram. I don't think this info was sent to the beta-testers, sorry. Matt ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
X-server for the mpc823 LCD controller?
> I would like to run X-windows (or something similar) on my custom mpc823 > board. So I'm looking for a X-server for the mpc823 LCD > controller, is there > any one out there? Check out http://www.microwindows.org It is a small graphics engine with a Win32 API and a X-like API. The current verison supports Embedded Planet's LinuxPlanet box (0.88pre7, I think) btw, I am finishing up a touch screen driver for LinuxPlanet that works with Microwindows. Check the Montavista ftp site in the next week or so. I will make another anouncement when it is there. > > I have used the RPXL LCD frame buffer on my RPXL board, with the program > dispbmp. Is the source code available for this program? If you bought a LinuxPlanet, you should have the source on the CD from Embedded Planet. > Can any existing graphical server use this frame buffer? I don't think so (execpt microwindows). I am not totally familiar with the linux fb device, but I believe the lcd driver needs a little more work to look like a linux fb device. Or you will need to hack the server to use our lcd driver. Matthew Locke Embedded Planet S/W Development ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Looking for inetd, telnetd, ftpd, httpd source/binaries for MPC8xx
Montavista currently has both source and binaries available for all those and more on thier ftp site. http://www.mvista.com Matthew Locke Embedded Planet > -Original Message- > From: owner-linuxppc-embedded at lists.linuxppc.org > [mailto:owner-linuxppc-embedded at lists.linuxppc.org]On Behalf Of Rodney > Davies > Sent: Wednesday, March 15, 2000 6:45 PM > To: 'linuxppc-embedded at lists.linuxppc.org' > Subject: Looking for inetd, telnetd, ftpd, httpd source/binaries for > MPC8xx > > > > Hi all! > > I was wondering if the inetd networking has been made for embedded linux? > ...I guess along with in.telnetd, in.ftpd etc etc...?? > > I'm currently trying to port inetd over myself... will let you know how I > go... > > Cheers, > Rod > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Download timeout problems on Embedded Planet CLLF (was Patch for zsrec.c)
> I think you mean it's an issue with the EP implementation of tftp. Well... you didn't hear that from me:-) > Sounds great! If it's still using tftp, can you make sure they > get the timeout > handling right this time? :-) Definitely. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Download timeout problems on Embedded Planet CLLF (was Patch for zsrec.c)
> Are other people also having problems with download timeouts on > Embedded Planet > boards? (or even if you're not, I'd love to hear what you're > doing different). I assume you mean using tftp. If so ... I have had the download timeout problems. It is not related (directly) to the EP boards. It is more of a tftp issue. If there is alot of network traffic, tftp might not receive its packets in time. If you have a large file with alot of network traffic, it defintely will timeout. I worked around these issues by isolating the EP and host from the other network traffic and/or splitting the srec file into smaller parts. PS: we are working on a ELF binary dnload capabiltiy, watch EPs website next month. That will speed up the dnload. Matthew Locke Senior Software Engineer Embedded Planet ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
