>Yes. If you see how to do it - patches are welcome. One of the possible
>ways is to create a structure when you register driver, remove it upon
>rmmod, replace ->b_dev and friends with pointers to that structure and
>make the removal of this beast invalidate the buffers.
Wouldn't it be easye
On Fri, Oct 13, 2000 at 04:40:45PM +, Thorsten Kranzkowski wrote:
> Since I received a success report for 2.4.0pre8 for the very same board
> but compiled with 2.96.2 I tend to think that it's indeed the compiler.
^^
2.95.2 of course - friday 13th :-)
--
| Thorsten K
On Fri, Oct 13, 2000 at 10:13:11AM +0900, Tom Holroyd wrote:
> On Thu, 12 Oct 2000, Thorsten Kranzkowski wrote:
> >
> > Huh - your floppy is working?
> > gcc version 2.96 2925 (experimental)
>
> Mine works OK, except for that invalidate on last close thing (how do I go
> back to the old beh
On Fri, 13 Oct 2000, Guest section DW wrote:
> the command openflop:
> #include
> main(){
> int fd = open("/dev/fd0", O_RDONLY);
> pause();
> }
sh -c 'kill -SIGSTOP $$' each time after inserting a floppy, and to kill it
> before taking the floppy
On Fri, Oct 13, 2000 at 10:13:11AM +0900, Tom Holroyd wrote:
> Mine works OK, except for that invalidate on last close thing
> (how do I go back to the old behavior? Why was it changed?).
You go back to the old behaviour by commenting out the
invalidate_buffers call in
if (atomic_dec_an
On Thu, 12 Oct 2000, Thorsten Kranzkowski wrote:
> > > Alpha DP264 (UP), SCSI, floppy
> > >
> > > ... if I read from
> > > /dev/fd0, it used to buffer the whole thing, so a second read would be
> > > fast -- now it hits the floppy again.
>
> Huh - your floppy is working?
>
> Mine does not (wit
6 matches
Mail list logo
