I agree with KH that current iso transmit code be removed. Since the
original code auther doesnt think the model is good and not working, why put
it in the code base? remove now is much better than remove later. what's the
advantage to build code further on the not so good framework as later may
collapse?

By the way, I dont quite understand the use for IP over 1394 and who is the
target user. Any one knows? I think the linux 1394 driver model is  quite
good and I realize it may be a good idea to use its arch model. Now I am
testing it now.


----- Original Message -----
From: "James Chacon" <jmc@netbsd.org>
To: <ww@styx.org>
Cc: "James Chacon" <jmc@netbsd.org>; "HAYAKAWA Koichi" <haya@netbsd.org>;
<current-users@netbsd.org>; <tech-kern@netbsd.org>
Sent: Thursday, June 12, 2003 7:23 AM
Subject: Re: IEEE 1394 isochronous transmission code will be removed.


> Umm...not for anyone to easily see/know it's there to work with unless
they
> happened to have already seen this thread.
>
> James
>
> >
> >it'll still be in the cvs...
> >
> >On Wed, Jun 11, 2003 at 11:38:40AM -0400, James Chacon wrote:
> >> If there are no plans for developing a new one, then leave the existing
> >> as-is. Removing even semi-working code because it's not perfect isn't a
> >> good idea as it then prevents other people from possibly improving it
later.
> >>
> >> James
> >>
> >> >
> >> >From: James Chacon <jmc@netbsd.org>
> >> >Subject: Re: IEEE 1394 isochronous transmission code will be removed.
> >> >Date: Mon, 9 Jun 2003 00:33:07 -0400 (EDT)
> >> >Message-ID: <200306090433.AAA14016@chacons.net>
> >> >
> >> > > Why not leave it there for now and then insert a new model later?
If it's
> >> > > incomplete today folks should be able to experiment with it rather
than have
> >> > > it yanked out...
> >> > >
> >> > > James
> >> >
> >> >Yes, you are right.  But it is imcomplete and modelled not
> >> >very good...
> >> >
> >> >I want to know whether anyone working on it.  If it has been
> >> >abandoned and there are no plan of using it, I want to
> >> >remove it in the future, regardless of development of new
> >> >driver.
> >> >
> >> >Right now I have no plan of developing new iso transmission
> >> >driver.  So I'm expecting other programmers will work on
> >> >this issue;-)
> >> >--
> >> >KH
> >> >
> >> >
> >> >
> >>
> >
> >
> >
>