From: Bruno Randolf <br1@4g-systems.de>
To: Alexander Popov <s_popov@prosyst.bg>
Cc: linux-mips@linux-mips.org
Subject: Re: Mycable XXS board
Date: Fri, 7 Mar 2003 16:47:13 +0100 [thread overview]
Message-ID: <200303071647.13275.br1@4g-systems.de> (raw)
In-Reply-To: <1047040846.10649.10.camel@adsl.pacbell.net>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
hello!
we are also working with this board and it it supported thru the Pb1500 board
configuration of the linux-mips.org kernel. we use the 2_4 branch and some
patches of pete (ftp://ftp.linux-mips.org/pub/linux/mips/people/ppopov). with
these patches i can already see my pci cards (but i dont yet have a driver
for them). usb does not yet work - it complains that it cannot assign new
numbers to the devices. the flash chip (AM29LV641DL) is also not recognized
yet.
if you dont use YAMON, you have to add a patch to deal with the nonexistent
command line parameters. i attached it for you, but its an ugly hack.
and to enable one of the ethernet ports you can use the second patch. it's
also quite a hack, cause it does not yet deal with the second port...
bruno
On Friday 07 March 2003 13:40, you wrote:
> On Fri, 2003-03-07 at 04:36, Alexander Popov wrote:
> > Hi all,
> >
> > Has anyone used the kernel on a Mycable XXS board ( it has Alchemy au1500
> > )... What CPU type should I choose for the au1500? R5000? Sorry for the
> > lame question but I haven't used MIPS-based boards and I know nothing
> > baout the CPU...
>
> Given that the board has an Alchemy Au1500 CPU, I would say you should
> chose the Au1500 :) Start with the Pb1500 board port that's in
> linux-mips.org. Maybe, just maybe, a Pb1500 kernel will boot fine on
> your board. And if it doesn't, creating a port for the above mentioned
> board should be fairly easy.
>
> Pete
[-- Attachment #2: cfc_startup.diff --]
[-- Type: text/x-diff, Size: 1381 bytes --]
--- arch/mips/au1000/common/prom.c Wed Dec 12 19:30:52 2001
+++ arch/mips/au1000/common/prom.c Tue Feb 4 00:41:08 2003
@@ -62,21 +62,21 @@
void prom_init_cmdline(void)
{
- char *cp;
- int actr;
+// char *cp;
+// int actr;
- actr = 1; /* Always ignore argv[0] */
+// actr = 1; /* Always ignore argv[0] */
- cp = &(arcs_cmdline[0]);
- while(actr < prom_argc) {
- strcpy(cp, prom_argv[actr]);
- cp += strlen(prom_argv[actr]);
- *cp++ = ' ';
- actr++;
- }
- if (cp != &(arcs_cmdline[0])) /* get rid of trailing space */
- --cp;
- *cp = '\0';
+// cp = &(arcs_cmdline[0]);
+// while(actr < prom_argc) {
+// strcpy(cp, prom_argv[actr]);
+// cp += strlen(prom_argv[actr]);
+// *cp++ = ' ';
+// actr++;
+// }
+// if (cp != &(arcs_cmdline[0])) /* get rid of trailing space */
+// --cp;
+// *cp = '\0';
}
@@ -88,17 +88,17 @@
* Environment variables are stored in the form of "memsize=64".
*/
- t_env_var *env = (t_env_var *)prom_envp;
- int i;
+// t_env_var *env = (t_env_var *)prom_envp;
+// int i;
- i = strlen(envname);
+// i = strlen(envname);
- while(env->name) {
- if(strncmp(envname, env->name, i) == 0) {
- return(env->name + strlen(envname) + 1);
- }
- env++;
- }
+// while(env->name) {
+// if(strncmp(envname, env->name, i) == 0) {
+// return(env->name + strlen(envname) + 1);
+// }
+// env++;
+// }
return(NULL);
}
[-- Attachment #3: au1000_eth_BCM5222_hack.diff --]
[-- Type: text/x-diff, Size: 600 bytes --]
--- ../linux-mips-2_4-cvs-clean/drivers/net/au1000_eth.c Wed Dec 11 07:12:30 2002
+++ drivers/net/au1000_eth.c Fri Feb 7 14:37:49 2003
@@ -471,6 +471,7 @@
} mii_chip_table[] = {
{"Broadcom BCM5201 10/100 BaseT PHY", 0x0040, 0x6212, &bcm_5201_ops },
{"Broadcom BCM5221 10/100 BaseT PHY", 0x0040, 0x61e4, &bcm_5201_ops },
+ {"Broadcom BCM5222 10/100 BaseT PHY", 0x0040, 0x6322, &bcm_5201_ops },
{"AMD 79C901 HomePNA PHY", 0x0000, 0x35c8, &am79c901_ops },
{"AMD 79C874 10/100 BaseT PHY", 0x0022, 0x561b, &am79c874_ops },
{"LSI 80227 10/100 BaseT PHY", 0x0016, 0xf840, &lsi_80227_ops },
next prev parent reply other threads:[~2003-03-07 15:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 12:36 Mycable XXS board Alexander Popov
2003-03-07 12:40 ` Pete Popov
2003-03-07 15:47 ` Bruno Randolf [this message]
2003-03-07 18:13 ` Jun Sun
2003-03-07 20:12 ` Dan Malek
2003-03-07 21:39 ` Jun Sun
2003-03-07 21:54 ` Dan Malek
2003-03-11 10:30 ` Bruno Randolf
2003-03-11 15:17 ` Pete Popov
2003-03-11 21:43 ` Eric DeVolder
2003-03-11 21:57 ` Dan Malek
2003-03-13 13:08 ` Bruno Randolf
2003-03-13 16:03 ` Dan Malek
2003-03-13 17:23 ` Bruno Randolf
2003-03-13 17:50 ` Dan Malek
2003-03-13 18:07 ` Pete Popov
2003-03-11 15:59 ` Tiemo Krueger - mycable GmbH
-- strict thread matches above, loose matches on Subject: below --
2003-03-10 8:27 Tiemo Krueger - mycable GmbH
2003-03-10 8:33 Tiemo Krueger - mycable GmbH
2003-03-10 9:41 ` Alexander Popov
2003-03-10 9:41 ` Alexander Popov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200303071647.13275.br1@4g-systems.de \
--to=br1@4g-systems.de \
--cc=linux-mips@linux-mips.org \
--cc=s_popov@prosyst.bg \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox