From: Andrew May <acmay@acmay.homeip.net>
To: linuxppc-embedded@lists.linuxppc.org
Cc: amay@viasat.com, akuster@pacbell.net
Subject: status of 2_4_devel
Date: Tue, 1 Oct 2002 13:01:10 -0700 [thread overview]
Message-ID: <20021001200110.GA10094@acmay.homeip.net> (raw)
I have been off doing other stuff so I haven't done a resync of the tree
since June.
First thing I ran into was a compile problem with the IBM OCP ethernet driver.
Have things really not even compiled for the 405GP since Aug 22? This little
patch should fix that problem.
==== ibm_ocp_enet.c 1.41 vs edited =====
--- 1.41/drivers/net/ibm_ocp/ibm_ocp_enet.c Mon Sep 30 18:34:10 2002
+++ edited/ibm_ocp_enet.c Mon Sep 30 19:45:24 2002
@@ -1195,7 +1195,7 @@
/* if (tmp_em0isr & EMAC_ISR_MOS ) fep->stats.ZZZ++; */
/* if (tmp_em0isr & EMAC_ISR_MOF ) fep->stats.ZZZ++; */
- ppc405_bl_mac_eth_dump(dev, tmp_em0isr);
+ ppc405_bl_mac_eth_dump((struct net_device*)dev_instance, tmp_em0isr);
out_be32(&emacp->em0isr, tmp_em0isr);
}
Next I ran into problems with the UART init. Looking at arch/ppc/kernel/ocp_uart.c
I was absolutely amazed. Why would you call early_serial_init with values from
rs_table when early_serial_init puts the values right back into rs_table?
When I had John post the patch to add the call to early_s..., it was to
get the base baud rate dynamically from the clock speed, so the value
didn't need to be compiled in. As it is now the code in early_uart_init
is completely pointless and just wastes space.
http://lists.linuxppc.org/linuxppc-embedded/200204/msg00129.html
ps: my home email is having problems so I cc'd my work/outlook account.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2002-10-01 20:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021001200110.GA10094@acmay.homeip.net \
--to=acmay@acmay.homeip.net \
--cc=akuster@pacbell.net \
--cc=amay@viasat.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).