1. 05 Jun, 2003 7 commits
    • Hideaki Yoshifuji's avatar
      [netdrvr] C99 initializers for arcnet · 7107a09c
      Hideaki Yoshifuji authored
      7107a09c
    • Scott Feldman's avatar
      [PATCH] remove ethtool privileged references · 5443b474
      Scott Feldman authored
      dev_ioctl already checks capable(CAP_NET_ADMIN) for SOICETHTOOL, so
      privileged reference are not necessary.
      5443b474
    • Scott Feldman's avatar
      [PATCH] 10GbE ethtool support · c4a875e5
      Scott Feldman authored
      Add 10GbE support for ethtool.
      c4a875e5
    • Zwane Mwaikambo's avatar
      [PATCH] cli/sti cleanup for fmvj18x · f86e71e8
      Zwane Mwaikambo authored
      This one should be safe as we're protected by the xmit_lock in all instances
      f86e71e8
    • Jeff Garzik's avatar
      08d84e53
    • Simon Kelley's avatar
      [netdrvr] add atmel[_cs], new wireless driver · bd75dd8c
      Simon Kelley authored
      Attached is a driver for Atmel at76c50x WiFi cards. This code started
      out as a GPL release from Atmel of pretty horrible quality and I've
      extensively re-worked it with the aim of making it acceptable in the
      kernel. Please could you take a look and either pass it into the patch
      stream or let me know what's wrong with it?
      
      The code has been tested on at least three different brand cards by
      different people. Jean Tourrilhes took a look at an earlier version an
      was positive. He's put incorporating this into 2.6 as a priority 1.
      The patch works fine on 2.5.70.
      
      The firmware issue has been addressed now. The only firmware in the
      driver is a small stub which reads the MAC address from NVRAM on the
      card. The source for that is included so there are no GPL issues. The
      main firmware is loaded from userspace using Manuel Estrada Sainz's
      sysfs firmware class. I know that the  patch for that has been
      accepted but it hasn't turned up anywhere I can see yet. The 
      driver compiles fine even without the firmware class. I've made a
      package of the firmware images which is available from my website.
      
      The remaining issues with the driver are migrating PCMCIA to the new
      driver model and PCI support. I'm happy to produce followup patches as
      the PCMCIA system gets evolved to the new driver model: the timing on
      that is controlled by others. This set of chips includes a PCI version
      and the driver should support that, but AFAIK there is no PCI hardware
      available anywhere. If Atmel can provide me with some it will be
      simple to add PCI support.
      
      The driver uses the CRC32 library module and the firmware loader. I've
      not put in dependencies on those, but when the lastest set of patches
      go into Kconfig I'll set it up so that selecting the Atmel driver
      selects CRC32 and FW_LOADER too.
      bd75dd8c
    • Stephen Hemminger's avatar
      [PATCH] sb1000 driver bugs · b1871948
      Stephen Hemminger authored
      Inspecting the sb1000 driver showed some interesting bugs:
      	- net device pointer is used before the device is allocated; gcc
      	  does catch this.
      	- unregister is called even though device not registered successfully
      	- net device is not freed on remove.
      
      Compiles but don't have hardware to test.  Don't know how it ever worked though.
      b1871948
  2. 04 Jun, 2003 5 commits
  3. 05 Jun, 2003 2 commits
    • Russell King's avatar
      [ARM] Tidy up Integrator core support. · 8698cff8
      Russell King authored
      This merges arch.c, irq.c and mm.c into one core file for this
      platform; it's pointless keeping these separate.
      8698cff8
    • Russell King's avatar
      [ARM] Convert platform devices to use platform_device · 4f00f1c2
      Russell King authored
      Since struct platform_device now has the ability to pass resources,
      defined by the platform to the device driver, we can now use this
      to handle platform specific devices.  One such instance is the
      StrongARM SA1111 companion chip, which can appear in various address
      spaces, and connected to different IRQ lines depending on how many
      cups of coffee the hardware designer had, the direction of the wind
      outside the designers office that day.
      
      We also convert some of the other StrongARM peripheral on-chip
      devices to use struct platform_device.
      
      ARM also provides a platform_add_devices() function which can be
      used by platform code to bulk-register a tabular set of platform
      devices.
      4f00f1c2
  4. 04 Jun, 2003 26 commits