headers
enami tsugutomo | 1 Apr 2004 04:06
Picon

Re: uscanner* and 2.0

> > Any instance of this is either a bug in SANE or a bug in ugen(4). Do you
> > still have that scanner?
> 
> Yes, but I need to reconnect it before I can try it. Do you have a
> configuration example how to use a scanner with ugen(4) and SANE?

I tried last nigtht with my scanner (epson GT-9700F), and ugen needs
following modification in order to work with scanimage.  Though, I'm
not sure if ugen.c is really the right place to fix.

enami.

Index: ugen.c
===================================================================
RCS file: /cvsroot/src/sys/dev/usb/ugen.c,v
retrieving revision 1.66
diff -c -r1.66 ugen.c
*** ugen.c	4 Sep 2003 03:47:03 -0000	1.66
--- ugen.c	1 Apr 2004 01:45:05 -0000
***************
*** 306,311 ****
--- 306,325 ----
  			sce->sc = sc;
  			sce->edesc = ed;
  			sce->iface = iface;
+ 			/*
+ 			 * For some device, the order to open pipe is
+ 			 * importatnt.
+ 			 */
+ 			if (1 &&
(Continue reading)

Permalink | Reply | 3 comments |
headers
D'Arcy J.M. Cain | 1 Apr 2004 04:12
Picon

Re: uscanner* and 2.0

On March 31, 2004 09:06 pm, enami tsugutomo wrote:
> I tried last nigtht with my scanner (epson GT-9700F), and ugen needs
> following modification in order to work with scanimage.  Though, I'm
> not sure if ugen.c is really the right place to fix.

Would you like to file a PR with these changes?  Perhaps someone who knows the 
code well can comment on where it belongs if not here.

http://www.netbsd.org/Misc/send-pr.html#submitting explains how to submit a PR 
if you are not familiar with the process.  It's pretty simple.

--

-- 
D'Arcy J.M. Cain <darcy <at> netbsd.org>
http://www.NetBSD.org/
Permalink | Reply | 0 comments |
headers
Jun-ichiro itojun Hagino | 1 Apr 2004 04:59

Re: vi changes?

> Of couse, once you start using autoindent, and have tabs, vi gets
> completely confused about the column position anyway!
> I also suspect than 'nvi' (as on linux) contains some of the AT&T vi
> source!  It is far too 'bug compatible' to be a clean room copy.

	from what i see i don't think nvi does not contain original vi source.
	nvi really tries very hard to be bug-compatible.

itojun
Permalink | Reply | 1 comment |
headers
Jun-ichiro itojun Hagino | 1 Apr 2004 05:09

Re: vi changes?

> > Of couse, once you start using autoindent, and have tabs, vi gets
> > completely confused about the column position anyway!
> > I also suspect than 'nvi' (as on linux) contains some of the AT&T vi
> > source!  It is far too 'bug compatible' to be a clean room copy.
> 
> 	from what i see i don't think nvi does not contain original vi source.

	oops, "i think nvi does not contain..."

itojun
Permalink | Reply | 0 comments |
headers
Charles M. Hannum | 1 Apr 2004 05:30

Re: vi changes?

On Wednesday 31 March 2004 08:46 pm, David Laight wrote:
> I also suspect than 'nvi' (as on linux) contains some of the AT&T vi
> source!  It is far too 'bug compatible' to be a clean room copy.

nvi does not contain any original vi code.  The reason it's so bug-compatible 
is simply that Keith is (was?) insane.  And several people (including myself) 
complained about lots of obscure things it didn't do "right" in the early 
days.
Permalink | Reply | 5 comments |
headers
Herb Peyerl | 1 Apr 2004 05:47

Re: vi changes?

On Thu, Apr 01, 2004 at 03:30:24AM +0000, Charles M. Hannum wrote:
> nvi does not contain any original vi code.  The reason it's so bug-compatible 
> is simply that Keith is (was?) insane.  And several people (including myself) 
> complained about lots of obscure things it didn't do "right" in the early 
> days.

off topic but related.  Is anyone else seeing random and un-reproducible
SEGV's with 'nvi' in multi-buffer mode, most often when yanking and pasting
from one buffer to another?

It happens frequently enough that it's annoying but infrequently enough
that it's hard to reproduce.

---
Real PC Serial console & remote reset - The PC Weasel! http://www.realweasel.com
Permalink | Reply | 3 comments |
headers
enami tsugutomo | 1 Apr 2004 06:38
Picon

Re: uscanner* and 2.0

> Would you like to file a PR with these changes?  Perhaps someone who
> knows the code well can comment on where it belongs if not here.

I've just post yesterday's my experience in my last mail and there is
nothing ready to file as a PR at this moment.

enami.
Permalink | Reply | 0 comments |
headers
John Nemeth | 1 Apr 2004 06:55
Picon
Favicon

Re: CVS commit: src/sys/dev/raidframe

On Jul 7,  9:15am, Greg Oster wrote:
} 
} Module Name:	src
} Committed By:	oster
} Date:		Sun Mar 21 21:08:08 UTC 2004
} 
} Modified Files:
} 	src/sys/dev/raidframe: rf_driver.c
} 
} Log Message:
} Yesterday's fix to rf_disks.c (rev 1.51) was necessary, but not
} sufficient to clobber this nasty little bug.  The behaviour observed
} was a panic when doing a 'raidctl -f' on a component when DAGs were
} in flight for the given RAID set.  Unfortunatly, the faulty behaviour

     My curiosity has finally gotten the better of me.  What is a DAG?
Besides a Directed Acyclic Graph.

}-- End of excerpt from Greg Oster
Permalink | Reply | 2 comments |
headers
Thor Lancelot Simon | 1 Apr 2004 07:05

Re: CVS commit: src/sys/dev/raidframe

On Wed, Mar 31, 2004 at 08:55:16PM -0800, John Nemeth wrote:
> On Jul 7,  9:15am, Greg Oster wrote:
> } 
> } Module Name:	src
> } Committed By:	oster
> } Date:		Sun Mar 21 21:08:08 UTC 2004
> } 
> } Modified Files:
> } 	src/sys/dev/raidframe: rf_driver.c
> } 
> } Log Message:
> } Yesterday's fix to rf_disks.c (rev 1.51) was necessary, but not
> } sufficient to clobber this nasty little bug.  The behaviour observed
> } was a panic when doing a 'raidctl -f' on a component when DAGs were
> } in flight for the given RAID set.  Unfortunatly, the faulty behaviour
> 
>      My curiosity has finally gotten the better of me.  What is a DAG?
> Besides a Directed Acyclic Graph.

Heh.  I think I'll let Greg explain RAIDframe-as-graph-solver -- but
that's exactly what it is.

--

-- 
 Thor Lancelot Simon	                                      tls <at> rek.tjls.com
   But as he knew no bad language, he had called him all the names of common
 objects that he could think of, and had screamed: "You lamp!  You towel!  You
 plate!" and so on.              --Sigmund Freud
Permalink | Reply | 0 comments |
headers
Geoff Wing | 1 Apr 2004 07:18
Picon

Re: CVS commit: src/sys/netinet (ip_compat.h 1-35 -> 1.36)

Darren Reed <darrenr <at> netbsd.org> typed:
: Module Name:	src
: Committed By:	darrenr
: Date:		Wed Mar 31 11:41:46 UTC 2004
: Modified Files:
: 	src/sys/netinet: ip_compat.h
: Log Message:
: COPYIN/COPYOUT macros need to call copyin/out on NetBSD rather than just use
: bcopy.

This update just killed ipfilter for me on i386 so I guess it's exposed some
other problem.

# ipf -E
SIOCFRENB: Bad address
# ipfstat
ioctl(SIOCGETFF): Bad address
....

Regards,
--

-- 
Geoff Wing : <gcw <at> pobox.com>
Permalink | Reply | 2 comments |

Gmane