Re: [ath9k-devel] [RFC 08/12] ath9k: get EEPROM contents from platform data on AHB bus

2009-01-06 Thread Sujith
Gabor Juhos wrote: > > Also, after addressing Christopher's comments, I don't think too many > > bus specific routines would remain. In that case would it be reasonable > > to just have a single file (bus.c, with appropriate ifdefs), instead > > of pci.c and ahb.c ? > > We will have 3 of them actu

Re: [ath9k-devel] [RFC 08/12] ath9k: get EEPROM contents from platform data on AHB bus

2009-01-05 Thread Gabor Juhos
Sujith írta: > Gabor Juhos wrote: >> +#ifndef _LINUX_ATH9K_PLATFORM_H >> +#define _LINUX_ATH9L_PLATFORM_H > > Typo ? Oops, yes. > Also, after addressing Christopher's comments, I don't think too many > bus specific routines would remain. In that case would it be reasonable > to just have a singl

[ath9k-devel] [RFC 08/12] ath9k: get EEPROM contents from platform data on AHB bus

2009-01-05 Thread Sujith
Gabor Juhos wrote: > +#ifndef _LINUX_ATH9K_PLATFORM_H > +#define _LINUX_ATH9L_PLATFORM_H Typo ? Also, after addressing Christopher's comments, I don't think too many bus specific routines would remain. In that case would it be reasonable to just have a single file (bus.c, with appropriate ifdefs)

[ath9k-devel] [RFC 08/12] ath9k: get EEPROM contents from platform data on AHB bus

2009-01-03 Thread Gabor Juhos
On the AR913x SOCs we have to provide EEPROM contents via platform_data, because accessing the flash via MMIO is not safe. Additionally different boards may store the radio calibration data at different locations. Signed-off-by: Gabor Juhos Signed-off-by: Imre Kaloz --- drivers/net/wireless/ath