Re: [PATCH 12/41] mxser: allow overlapping vector

2012-08-13 Thread Jiri Slaby
On 08/13/2012 03:50 AM, Rusty Russell wrote: > On Tue, 7 Aug 2012 21:47:37 +0200, Jiri Slaby wrote: >> For many cards, this saves some IO space because interrupt status port >> has precedence over the rest of ports on the card. Hence it can be >> mapped to a hole in I/O ports. >> >> Here we add

Re: [PATCH 12/41] mxser: allow overlapping vector

2012-08-13 Thread Jiri Slaby
On 08/13/2012 03:50 AM, Rusty Russell wrote: On Tue, 7 Aug 2012 21:47:37 +0200, Jiri Slaby jsl...@suse.cz wrote: For many cards, this saves some IO space because interrupt status port has precedence over the rest of ports on the card. Hence it can be mapped to a hole in I/O ports. Here we

Re: [PATCH 12/41] mxser: allow overlapping vector

2012-08-12 Thread Rusty Russell
On Tue, 7 Aug 2012 21:47:37 +0200, Jiri Slaby wrote: > For many cards, this saves some IO space because interrupt status port > has precedence over the rest of ports on the card. Hence it can be > mapped to a hole in I/O ports. > > Here we add a kernel parameter which allows that if a user

Re: [PATCH 12/41] mxser: allow overlapping vector

2012-08-12 Thread Rusty Russell
On Tue, 7 Aug 2012 21:47:37 +0200, Jiri Slaby jsl...@suse.cz wrote: For many cards, this saves some IO space because interrupt status port has precedence over the rest of ports on the card. Hence it can be mapped to a hole in I/O ports. Here we add a kernel parameter which allows that if a

[PATCH 12/41] mxser: allow overlapping vector

2012-08-07 Thread Jiri Slaby
For many cards, this saves some IO space because interrupt status port has precedence over the rest of ports on the card. Hence it can be mapped to a hole in I/O ports. Here we add a kernel parameter which allows that if a user wants to. But they need to explicitly enable it by a module

[PATCH 12/41] mxser: allow overlapping vector

2012-08-07 Thread Jiri Slaby
For many cards, this saves some IO space because interrupt status port has precedence over the rest of ports on the card. Hence it can be mapped to a hole in I/O ports. Here we add a kernel parameter which allows that if a user wants to. But they need to explicitly enable it by a module