linux-toradex.git/drivers/net/ioc3-eth.c, branch v2.6.16.40-rc1 Linux kernel for Apalis and Colibri modules [PATCH] IOC3: Replace obsolete PCI API 2005-11-18T18:29:41+00:00 Ralf Baechle ralf@linux-mips.org 2005-11-13T10:13:05+00:00 70f1e002cfaad708ac561bcc6700dc50888999f5 Signed-off-by: Ralf Baechle <ralf@linux-mips.org> Signed-off-by: Jeff Garzik <jgarzik@pobox.com> 
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Signed-off-by: Jeff Garzik <jgarzik@pobox.com>
[SERIAL] IOC3: Update 8250 driver bits 2005-11-08T23:10:51+00:00 Ralf Baechle ralf@linux-mips.org 2005-11-08T23:10:51+00:00 15a93807826a5cbffb47d6bfbeeee108d6da1dbc Update the support for the 16550 present on most IOC3 configurations to use the current API. Signed-off-by: Ralf Baechle <ralf@linux-mips.org> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
Update the support for the 16550 present on most IOC3 configurations to use
the current API.

Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[PATCH] IOC3 fixes 2005-08-18T20:59:14+00:00 Ralf Baechle ralf@linux-mips.org 2005-08-02T10:01:27+00:00 852ea22ab24df4c64c0211c3b6d6358eb0e759f9 - Using the right register clearly improves chances of getting the MII code and thus the driver working at all. - On startup check the media type before setting up duplex or we might spend the first 1.2s with a wrong duplex setting. - Get rid of whitespace lines. Signed-off-by: Jeff Garzik <jgarzik@pobox.com> 
 - Using the right register clearly improves chances of getting the MII
   code and thus the driver working at all.
 - On startup check the media type before setting up duplex or we might
   spend the first 1.2s with a wrong duplex setting.
 - Get rid of whitespace lines.
Signed-off-by: Jeff Garzik <jgarzik@pobox.com>
Linux-2.6.12-rc2 2005-04-16T22:20:36+00:00 Linus Torvalds torvalds@ppc970.osdl.org 2005-04-16T22:20:36+00:00 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip! 
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!