Re: [U-Boot] [PATCH 1/2] NET: NE2000: Cleanup IO accessors

2012-07-13 Thread Marek Vasut
Dear Joe Hershberger, > Hi Marek, > > On Fri, Dec 16, 2011 at 2:36 PM, Marek Vasut wrote: > >> On Friday 16 December 2011 13:13:33 Marek Vasut wrote: > >> > On Friday 16 December 2011 12:33:53 Mike Frysinger wrote: > >> > > rename ISA_OFFSET to CONFIG_NE2000_IO_OFFSET, then move the "2" to > >>

Re: [U-Boot] [PATCH 1/2] NET: NE2000: Cleanup IO accessors

2012-07-10 Thread Joe Hershberger
Hi Marek, On Fri, Dec 16, 2011 at 2:36 PM, Marek Vasut wrote: >> On Friday 16 December 2011 13:13:33 Marek Vasut wrote: >> > On Friday 16 December 2011 12:33:53 Mike Frysinger wrote: >> > > rename ISA_OFFSET to CONFIG_NE2000_IO_OFFSET, then move the "2" to >> > > CONFIG_NE2000_IO_STRIDE, and move

Re: [U-Boot] [PATCH 1/2] NET: NE2000: Cleanup IO accessors

2011-12-16 Thread Marek Vasut
> On Friday 16 December 2011 13:13:33 Marek Vasut wrote: > > On Friday 16 December 2011 12:33:53 Mike Frysinger wrote: > > > rename ISA_OFFSET to CONFIG_NE2000_IO_OFFSET, then move the "2" to > > > CONFIG_NE2000_IO_STRIDE, and move them both to the board config header. > > > then you get one unifie

Re: [U-Boot] [PATCH 1/2] NET: NE2000: Cleanup IO accessors

2011-12-16 Thread Mike Frysinger
On Friday 16 December 2011 13:13:33 Marek Vasut wrote: > On Friday 16 December 2011 12:33:53 Mike Frysinger wrote: > > rename ISA_OFFSET to CONFIG_NE2000_IO_OFFSET, then move the "2" to > > CONFIG_NE2000_IO_STRIDE, and move them both to the board config header. > > then you get one unified set: > >

Re: [U-Boot] [PATCH 1/2] NET: NE2000: Cleanup IO accessors

2011-12-16 Thread Marek Vasut
> On Monday 12 December 2011 05:17:49 Marek Vasut wrote: > > > On Sunday 11 December 2011 08:42:07 Marek Vasut wrote: > > > > > On Saturday 10 December 2011 20:09:30 Marek Vasut wrote: > > > > > > Introduce ne2k_register_io(in, out), which allows user to supply > > > > > > two functions. One for re

Re: [U-Boot] [PATCH 1/2] NET: NE2000: Cleanup IO accessors

2011-12-16 Thread Mike Frysinger
On Monday 12 December 2011 05:17:49 Marek Vasut wrote: > > On Sunday 11 December 2011 08:42:07 Marek Vasut wrote: > > > > On Saturday 10 December 2011 20:09:30 Marek Vasut wrote: > > > > > Introduce ne2k_register_io(in, out), which allows user to supply > > > > > two functions. One for reading data

Re: [U-Boot] [PATCH 1/2] NET: NE2000: Cleanup IO accessors

2011-12-12 Thread Marek Vasut
> On Sunday 11 December 2011 08:42:07 Marek Vasut wrote: > > > On Saturday 10 December 2011 20:09:30 Marek Vasut wrote: > > > > Introduce ne2k_register_io(in, out), which allows user to supply two > > > > functions. One for reading data from the card, the other for writing > > > > data to the card.

Re: [U-Boot] [PATCH 1/2] NET: NE2000: Cleanup IO accessors

2011-12-11 Thread Mike Frysinger
On Sunday 11 December 2011 08:42:07 Marek Vasut wrote: > > On Saturday 10 December 2011 20:09:30 Marek Vasut wrote: > > > Introduce ne2k_register_io(in, out), which allows user to supply two > > > functions. One for reading data from the card, the other for writing > > > data to the card. Then intr

Re: [U-Boot] [PATCH 1/2] NET: NE2000: Cleanup IO accessors

2011-12-11 Thread Marek Vasut
> On Saturday 10 December 2011 20:09:30 Marek Vasut wrote: > > Introduce ne2k_register_io(in, out), which allows user to supply two > > functions. One for reading data from the card, the other for writing data > > to the card. Then introduce drivers' private data, which carry pointers > > to these

Re: [U-Boot] [PATCH 1/2] NET: NE2000: Cleanup IO accessors

2011-12-10 Thread Mike Frysinger
On Saturday 10 December 2011 20:09:30 Marek Vasut wrote: > Introduce ne2k_register_io(in, out), which allows user to supply two > functions. One for reading data from the card, the other for writing data > to the card. Then introduce drivers' private data, which carry pointers to > these functions

[U-Boot] [PATCH 1/2] NET: NE2000: Cleanup IO accessors

2011-12-10 Thread Marek Vasut
Introduce ne2k_register_io(in, out), which allows user to supply two functions. One for reading data from the card, the other for writing data to the card. Then introduce drivers' private data, which carry pointers to these functions and are passed throughout the driver. The private data will carr