>
>>> Could anyone explain to me what I am doing wrong? make installworld fails
>>> each time with the following error
>>>
>>> ===> stand/i386/libi386 (install)
>>> ===> stand/i386/loader_4th (install)
>>> strip -R .comment -R .note -o loader_4th.bin loader_4th.sym
>>> btxld -v -f aout -e 0x2000
>> Could anyone explain to me what I am doing wrong? make installworld fails
>> each time with the following error
>>
>> ===> stand/i386/libi386 (install)
>> ===> stand/i386/loader_4th (install)
>> strip -R .comment -R .note -o loader_4th.bin loader_4th.sym
>> btxld -v -f aout -e 0x20 -o load
> On Tue, Jan 28, 2020, 4:57 AM Nick Hibma <mailto:n...@van-laarhoven.org>> wrote:
> > On 28/01 /2020, at 12:39, Toomas Soome > <mailto:tso...@me.com>> wrote:
> >
> >> On 28. Jan 2020, at 13:36, Nick Hibma >> <mailto:n...@van-laarhoven.
> On 28/01 /2020, at 12:39, Toomas Soome wrote:
>
>> On 28. Jan 2020, at 13:36, Nick Hibma wrote:
>>
>> Folks,
>>
>> Could anyone explain to me what I am doing wrong? make installworld fails
>> each time with the following error
>>
>>
it by specifying the full path to btxld in the stand/i386/*/Makefile.
Any pointers?
Nick Hibma
n...@van-laarhoven.org
-- Open Source: We stand on the shoulders of giants.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/li
That (with the return added, thanks Cy) worked like a charm.
Thanks for the fast response.
Nick Hibma
n...@van-laarhoven.org
-- Open Source: We stand on the shoulders of giants.
> On 21 Jan 2020, at 18:38, Alexander V. Chernikov wrote:
>
> 21.01.2020, 17:25, "Nick Hibma"
in advance for any help.
Nick Hibma
n...@van-laarhoven.org
-- Open Source: We stand on the shoulders of giants.
Unread portion of the kernel message buffer:
panic: Assertion in_epoch(net_epoch_preempt) failed at
/usr/src/sys/netinet/in.c:968
cpuid = 0
time = 1579626632
KDB: stack backtrace
hing that should be MFCed?
Regards,
Nick Hibma
n...@van-laarhoven.org
-- Open Source: We stand on the shoulders of giants.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
>> I created a new kernel config file from scratch, wondered what the
>> GEOM_PART_MBR option and friends were doing, search for them, didn't find
>> them in the tree, and deleted them from my config. But... de resulting disk
>> image didn't boot, because of the fact that it didn't recognise the MB
rts to build? I thought these
options were translated to stuff that cpp would use, but there are not uses of
for example GEOM_PART_MBR anywhere for example!
The only thing I was able to come up with, but could not figure out, was
FEATURE() doing some magic.
Thanks in advance for any pointers!
Nick
>> Should this be reported to the clang folks? Or is this to be expected when
>> abusing integer overflows this way?
>
> You will get an answer that this is expected. Add -fwrapv compiler flag
> to make signed arithmetic behave in a way different from the mine-field,
> or remove the code. For ke
at time_t is a 32 bit signed int.
Any pointers as to a general method of resolving these time_t issues?
Regards,
Nick Hibma
n...@van-laarhoven.org
-- Open Source: We stand on the shoulders of giants.
signature.asc
Description: Message signed with OpenPGP
>>
>> Nov 22 16:55:13 mercury kernel: swap_pager: out of swap space
>> Nov 22 16:55:13 mercury kernel: swap_pager_getswapspace(16): failed
>> Nov 22 16:55:13 mercury kernel: pid 22841 (tblgen), uid 0, was killed:
>> out of swap space
>>
>> This machine has 256MB of RAM and one 64MB swap partition
Hi,
Is there someone who is able to test support for the Huawei E3272 card with
CURRENT after 269584? I have not been able to confirm that it works.
Thanks in advance.
Nick
The change:
Author: n_hibma
Date: Tue Aug 5 12:08:50 2014
New Revision: 269584
URL: http://svnweb.freebsd.org/changese
Telit, Sierra Wireless, Option, etc. that
works with the Qualcomm chipsets. If you look in the cdc-wdm qmi driver in
Linux, it is a long list.
I could not find any mention of FreeBSD and QMI on the same page, so I assume
no one is working on it.
Nick Hibma
On 28 Feb 2014, at 02:14, Allan Jude wrote:
> With r262501
> (http://svnweb.freebsd.org/base?view=revision&revision=262501) importing
> the upgraded bcrypt from OpenBSD and eventually changing the default
> identifier for bcrypt to $2b$ it reminded me of a feature that is often
> seen in Forum s
>>> Yes, it's hard to store state on diskless systems... but I figured
>>> that anyone building a diskless system would know to not create a
>>> "run firstboot scripts" marker. And not all embedded systems are
>>> diskless...
>>
>> The embedded systems we create at $work have readonly root and mf
r the 'embedded systems' argument is of much use, as deleting the script
or flagging 'firstboot' is non-permanent.
Nick Hibma
n...@van-laarhoven.org
Want to feel like going on a holiday tomorrow? Try GTD.
On 14 Oct 2013, at 00:58, Colin Percival wrote:
> Hi all,
>
>
return (rt->rt_flags & RTF_BLACKHOLE ? 0 :
rt->rt_flags & RTF_HOST ? EHOSTUNREACH : ENETUNREACH);
}
Any pointers would be appreciated
Nick Hibma
n...@van-laarhoven.org
GTD: Time management for chaotic people.
r.
Ed was going to think this over, especially because a null console might come
in handy in jails.
Hope this is of use to anyone.
Nick Hibma
n...@van-laarhoven.org
How many todos are on YOUR To Do lists? - GTD
On 19 Feb 2013, at 10:03, Nick Hibma wrote:
> Ed sent me a answer to my rambli
pecifically for cases where you
have hardware without a console or potentially want to run init(8) in
a jail (though we're not there yet)."
http://svnweb.freebsd.org/base?view=revision&revision=232977
I'll try that, and will follow up here.
Nick Hibma
n...@van-laarhoven.org
Coll
esponse to 'echo > /dev/console' was 'Device
not configured'. I've added another CN_* priority to make sure a null console
does not take precedence over for example gdb console.
Any pointers as to who/how to resolve this issue? Any reason why the null
console appr
> Well, I think that that's what probe priorities actually for.
> I also think that typically ivars should be set by a bus driver. So maybe
> it's
> not such a good idea to pass data from probe to attach via ivars in child
> drivers.
> But I could be mistaken about that.
>
> Practically speakin
>> But we will continue the saga about this strange USB modem, if no
>> objections from your side :)
>> Is it possible to apply some quirk or some another workaround which
>> will solve the issue with endless USB_ERR_STALLED reported while it
>> trying to attach its builtin cardreader?
>
> Nick, d
> I think using fcntl is nicer than having a "close the cached connection"
> function, but I don't think I can get around this problem without
> changing something in libfetch.
I think libfetch should set the Close-On-Exec flag. It's wrong to have these
files propagate to children.
Nick_
Mark,
My 2 cents: Isn't it more appropriate to set FD_CLOEXEC on the fd?
fcntl(fd, F_SETFD, FD_CLOEXEC);
It doesn't sound like you ever want to have a cached connection be copied into
the child. Mum and child calling daddy using the same phone line isn't going to
make the conversation
[EMAIL PROTECTED]
> Current,
>
> I've gone through the USB hardware that I had laying around and added a
> series of entries in usbdevs. I submitted a couple of entries a while ago,
> but I guess the email got lost in the noise. Who should I contact about
> getting this committed?
>
> Regards,
>
Nick
> See XPT_CALC_GEOMETRY in /sys/dev/aic7xxx/aic7xxx_osm.c
>
> On Mon, 4 Nov 2002, Nick Hibma wrote:
> > Let's work on the 'proper' solution first.
> >
> > What SCSI commands are suitable for getting the geometry, generically
> > on a device?
> &g
Hm, the only one that does something different is the iir/iir.c driver.
I guess the best thing is to just copy what's in the aha driver.
Nick
> >
> > Let's work on the 'proper' solution first.
> >
> > What SCSI commands are suitable for getting the geometry, generically
> > on a device?
>
> Hmm
Let's work on the 'proper' solution first.
What SCSI commands are suitable for getting the geometry, generically
on a device?
Nick
> fdisk likely should do something sane in the face of such insanity,
> but it is unclear what and fdisk is a royal pita to work on anyway :-(
>
> Warner
>
>
--
[
> Well the short version of the problem is that "fdisk -BI " works
> on -stable to get a FreeBSD partition on the Compact Flash. This does
> not work on -current anymore. I have traced that back to the commit
> in umass.c rev 1.61 that removed the fake geometry setting and just
> leave the cylinder
USB is only the transport. It doesn't add or remove functionality (the
only exception being probing for LUNs on CBI devices). If you want to
determine the geometry you will have to do this through SCSI commands. I
was hoping that the CAM code would be smart enough to request the
details from the d
At the moment 'make load' does not work in /sys/modules. The attached
patch fixes that by using .OBJDIR instead of .CURDIR as the absolute
path to find the module at:
heidi:toor# make
Warning: Object directory not changed from original /usr/src-current/sys/modules/umass
...
heidi:toor# make load
> > As you can see, the patch is trivial, so I have no clue why this wasn't
> > left alone when they modified symfile.c. If I can be bothered I'll
> > submit it to them.
>
> Hmm. Looking at this patch, it seems it's complaining about being
> handed a hex value where it's looking for an address.
[0-9]+').
Nick
On Tue, 28 May 2002, Mark Peek wrote:
> At 3:54 PM +0200 5/28/02, Nick Hibma wrote:
> >I'm using a derivative of the .gdbinit.vinum files that is available in
> >the modules/vinum directory. For them to work the following patch is
> >needed in gdb52
I'm using a derivative of the .gdbinit.vinum files that is available in
the modules/vinum directory. For them to work the following patch is
needed in gdb52.
As you can see, the patch is trivial, so I have no clue why this wasn't
left alone when they modified symfile.c. If I can be bothered I'll
CONSPEED is used for both console and gdb. This is a bit awkward because
it means that I have to run my kernel console on 9600 baud on my
diskless box. The attached patch fixes this by introducing another
variable GDBSPEED.
The patch makes the default for GDBSPEED 9600, so anyone who uses a
high
device_set_ivars is always called (in usbd_probe_and_attach) with as an
argument a stack variable. Also, the ivar is not stored or anything in
the if_aue.c driver. So this problem sounds like a problem in revisions
of various files.
Please check that your kernel modules kernel are in sync. Do th
This looks like an electrical problem. What happens if you connect the
mouse directly to the machine, without any hubs?
Nick
On Sun, 23 Dec 2001, Raman Ng wrote:
> Hello all,
>
> I have already sent a mail about this problem before.
> I am a newbie of
> FreeBSD. This time I attached the dme
It would be trivial to write a driver, like uscanner, that does the
collection of two endpoints into one bidirectional file descriptor.
Endpoints are the pipes that USB communicates over, and due to sloppy
documentation in the USB spec. implementors of firmware didn't realise
that 1-in and 1-out
Definitely the drivers. UHCI is a pile of that stuff that smells.
Nick
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel O'Connor
> Sent: 11 November 2001 03:21
> To: Jim Bryant
> Cc: [EMAIL PROTECTED]; Michael Class
> Subject: Re: USB and SMP
Yes. I have no idea why phk has not done this.
As this is a purposeful panicing of systems that worked fine before, I
presume that someone is keeping track of the problems that are occurring
and going to do something about it? Or is this a bad case of 'someone
else's problem'?
Nick
On Tue, 30
Try [EMAIL PROTECTED] for more information.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Bryant
> Sent: 20 September 2001 15:19
> To: Konstantin Chuguev
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: USB Multimedia Card (MMC) read
Why don't you add an early-out for namelength => 15 or put the
if-statement in the loop:
Index: machine.c
===
RCS file: /home/ncvs/src/usr.bin/top/machine.c,v
retrieving revision 1.44
diff -u -r1.44 machine.c
--- machine.c 2001/05
I haven't looked at the OHCI spec for firewire at all, but it seems that
it was intended to be one specification. The OHCI spec puts a lot of
processing into the hands of the chip and the interaction is smart
enough to not require weird locking or delays (like the UHCI requires),
so it could be wo
Done.
Will be MFC-ed after 4.4-RELEASE.
On Thu, 23 Aug 2001, Eugene M. Kim wrote:
> Could anybody examine and commit the patch in the PR kern/29530? It fixes
> the support for KingByte USB Pen Drive by adding a quirk entry to
> src/sys/cam/scsi/scsi_da.c.
>
> It would be even better if this we
What you are doing doesn't work for sure. You are piping in and out of
the control enpoint which won't work. Perhaps
/usr/sbin/ppp -quiet -direct -nat <> /dev/ugen0.1
would work, if there is an endpoint 1-in and an endpoint 1-out and they
are both related to data transfer. Normally this
Please only back out the part that early outs on no interrupt for us at
all. There are some other changes in there which might indicate other
problems, like interrupt masks set wrong and interrupts from the
controller we are not but should be handling.
I didn't realise that PCI devices were that
Hardly any USB CD are supported as they are mainly ATAPI based.
Nick
On Mon, 9 Jul 2001, Person, Roderick wrote:
> I was reading the 5.0 Release notes and Hardware text. The release notes
> mention that usb support was added to the generic kernel and the
> installation program to allow for su
> > Could be, and I certainly don't know much about this code. But
> > it seems like the driver is being given reason to assume it has a
> > working device when it doesn't really have one. I assume the device
> > is unusable without its interrupt, so shouldn't it fail at probe or
> > attach time
You might want to specify in the comment what the arguments should look
like, like an example.
Nick
On Thu, 19 Apr 2001, Andrey A. Chernov wrote:
> On Thu, Apr 19, 2001 at 21:23:57 +0900, Kazutaka YOKOTA wrote:
> >
> > Maybe we should automatically add `-M 3' to flags for vidcontrol
> > in rc.
The device SHOULD work, but I have not been able to test it.
What kind of problems are you seeing?
Nick
>
> On 30-Mar-01 Adrian Browne wrote:
> > I was wondering if anyone has had any success with a usb isdn 3com modem or
> > other usb modem types. I have a usb scanner and printer that works
Sorry, me lame. I got distrcacted between committing usbdevs and its
derivative usbdevs.h.
I've committed the file and am doing a complete kernel build and will
commit uscanner.c 1.8 again after that.
Sorry.
Nick
On Thu, 4 Jan 2001, John Indra wrote:
> Dear all...
>
> Recent -CURRENT make b
Could you send me the output of dmesg and the complaints usbd is
producing?
Nick
On Tue, 21 Nov 2000 [EMAIL PROTECTED] wrote:
> What is the current state of the usbd? I keep getting messages that
> complain about a host controller error and a shutdown of the usb
> interface. And I don't even h
Whether a device is recognized by a driver depends on one thing
only: the probe routine in the driver. It either has to conform to the
specs and this device obviously doesn't, or it has to be supported by
the driver and therefore the IDs of the device need to be known.
The entries in usbdevs* ar
I'm not sure whether the problem of loading secondary usb modules is a
problem in 4.x but it is easy to try.
Boot a machine without usb support compiled in. after login, kldload
usb, then the miibus and then the if_aue modules. If that works, you
should be ok.
I cannot test this as at the momen
OTECTED]>
To: Nick Hibma <[EMAIL PROTECTED]>
Cc: USB BSD list <[EMAIL PROTECTED]>
Subject: Re: HP ScanJet 5200C
On 01-Nov-00 Nick Hibma wrote:
>
> [sound of someone slapping forehead]
>
> Do'h! Cut&paste error when copying stuff from ugen.
>
> H
Grmbl... Alan Clegg reported that the URL is not working. Not that there
is much to see yet, but the correct URL should be:
http://www.etla.net/~n_hibma/usb/uscanner-supported.pl
Sorry about that.
Nick
>
> FreeBSD now has preliminary support for USB scanners. You will need to
> have
FreeBSD now has preliminary support for USB scanners. You will need to
have SANE installed in order to use the uscanner driver. You can kldload
the uscanner driver.
Please do not contact me personally with questions on which scanner is
supported. You can get this information from
http:/
Did you check on the SANE home page whether your scanner is supported?
This is a USB driver and a trivial driver at that, with no vendor
specific code. So I won't be able to help.
Nick
> > I've quickly thrown together a driver for USB scanners. Unforunately, I
> > don't have a scanner availabl
I've quickly thrown together a driver for USB scanners. Unforunately, I
don't have a scanner available that is supported by SANE, so I can't
test it.
The driver is a rip-off of the ugen, with some bits of udbp thrown in
for good measure. It relies on a very recent version of usbdevs, so make
sur
Due to lack of time and other priorities I've not had a good look at the
driver for problems. I think that the initial submitter has a more
recent version available and that one should be tested. The NetBSD
version is also different and I need to look at what that one does.
Also, a patch to the
Hm, I had a look at the source code, and to be honest I can't find a
single reason why the path would be unset.
Did the CD reader detached itself from the bus in the meantime, or did
something like a bus error occur? Check your messages log around the
time the panic occurred to see if something
The word is that there is a problem but it is a software problem. For
some reason the virtual hub gives an IOERROR, but I haven't had the time
or seen the need to figure that one out.
It seems to be harmless though.
nick
> And what is the word on thise IOERROR's given by my kernel when its ini
Warning:
Do not use IBM Microdrives in any USB based CF II readers, like the
SmartMedia ImageMate until further notice. I've had reports of 2 drives
breaking in a SmartMedia ImageMedia. They are PHYSICALLY broken and will
no longer work.
Nick
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
ECTED] USB project
http://www.etla.net/~n_hibma/
-- Forwarded message --
Date: Tue, 18 Jul 2000 13:16:16 -0700 (PDT)
From: Nick Hibma <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: cvs commit: src/sys/dev/ppbus ppb_base.c
n_hibma 2000/07/18 1
> Well, the one you committed doesn't have the notification support I
> added, or the serial state bits that are in usbcdc.h. Do you need/want
> copies of the one I've been working on?
Yes, please. I must have them somewhere, but it might be a better idea
to get your latest version.
> Looks like
Right, I finally committed the driver you sent me. let me know if I've
made a mistake and committed the wrong one.
Mike, which Supra modem do you have? I've got a SupraMax 56K modem,
SUP2920 and it gives me a rainforest worth of endpoints, not somethig
that looks like a ACM CD Class device.
Ni
Could people, when posting these kinds of requests, add a one sentence
outline of what the PR / web page contains? Most people do not take the
time to look at the page if there is no barebones description of what
the information contains.
Thanks in advance.
Nick
P.S.: Keep posting them. It is
The opt_ files can be generated by the makefiles, so there is no reason
to remove those, see sys/modules/usb/Makefile
SRCS = bus_if.h device_if.h usb_if.h usb_if.c \
vnode_if.h \
opt_usb.h \
...
Any file called opt_*.h that is no
Fixed. Sorry.
On Thu, 6 Jul 2000, John Baldwin wrote:
> Charles Anderson wrote:
> >
> > # grep -r DIAGASSERT . (from /usr/src)
> > ./lib/libutil/fparseln.c: _DIAGASSERT(sp != NULL);
> > ./lib/libutil/fparseln.c: _DIAGASSERT(p != NULL);
> > ./lib/libutil/fparseln.c: _DIAGASSER
> > Could you mention the locations (as in a set of paths) that are
> > hands-off?
>
> I'll generate a list and put it somewhere (in the tree?) Good idea.
To be honest, I was more thinking of the heads up message. But it was
suggested to add it to the readme in netinet6/
Nick
--
[EMAIL PROTECTE
Yes, that will work. Sorry for breaking the build. The problem was some
stale files in my directories.
Nick
On Wed, 5 Jul 2000, Ollivier Robert wrote:
> According to Ollivier Robert:
> > buildworld is broken in libusb. Here is a tentative patch (I'm re-building
> > the world right now). The al
Could you mention the locations (as in a set of paths) that are
hands-off?
Nick
On Wed, 5 Jul 2000, Kris Kennaway wrote:
> As itojun has already posted, we are in the process of updating the
> KAME IPv6/IPSEC code in FreeBSD to the latest KAME sources.
>
> In importing the latest KAME code, we
Nothing has happened so far. I have a handspring now, but lack the time
currently to fix it. I'll have a go at it tomorrow if there is some
time left.
Nick
On Tue, 27 Jun 2000, Sascha Lucky Luck wrote:
> Hi all,
>
> what is the story with this bug? (If you want a hand with testing
> patches,
> > >From what I understood from dfr, when switching away from an interrupt
> > handler it is converted into a full thread. When the second piece of
> > hardware fires an interrupt it could then run at the same time.
>
> I thought of this almost immediately - it's a bad idea though because it
>
> : > usb tty and modems aren't supported, as far as I know.
> :
> : They're "nearly" there, AFAIR. I sent Nick some code a while back that
> : addressed the last problem I understood he had.
>
> I'll have to ask him about it then.
Picked it up, looked at it, got distracted by Reality and mu
> : Watch out - some USB modems are also WinModems.
Not WinModems as such (the USB link is too slow to feed the DSP, but
they do have proprietary protocols).
3COM modems are safe though. They are class compliant.
Nick
>
> usb tty and modems aren't supported, as far as I know. How can you
> te
CAM is not a valid example. It only touched the disk subsystem.
Merging back changes in blocks might not be possible. As Matthew
mentioned, Chuck's experience should be taken for a fact.
And bounding the amount of breakage is almost impossible without
squeezing the people doing the SMP work rea
More over, unlike other big project like CAM, this baby is going to
touch the gut of the OS.
It might be possible however for individual projects to move into a
separate branch.
Nick
> >What about doing the changes on a branch with the understanding that
> >the branch will *replace* HEAD when
What about shared interrupts? How are they going to be treated? With the
spl leaving the arena it somehow looks feasible to run one interrupt
source on two different threads if there are two pieces of hardware
attached to the same interrupt line.
>From what I understood from dfr, when switching
Although I would not like to put it as strongly as Warner does, I would
like to ask how the decision makers expect the rest of the project to
progress (the other 30 or so kernel committers) in a reasonable, not
too time consuming way.
Will there be a general mechanism for making patchsets agains
When loading modules with other modules in the same linker file,
depending on each other, currently the kernel linker chokes. Example:
the uhub, uhci, ohci and usb modules are (for unrelated reasons) linked
into one big file. It is however impossible currently to preload that
file because the dep
What about using uppercase names for
buf_complete -> BUF_COMPLETE
and friends to make it apparent that an indirect call is being made and
that the function might not be supported on that struct buf. Much like
newbus, kobj, and vnode ops.
Nick
On Wed, 14 Jun 2000, Poul-Henning Kamp wr
> Which host are you pilling from? I am slurping things out of
^^^
I've seen this post now three times and I still can't remember what word
I wanted to use there. :-) It must be age I guess...
Nick
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
> On this machine which runs -CURRENT from two days ago or so, I'm
> seeing frequent cvsup client failures of this type:
>
> TreeList failed: Network write failure: Connection closed
>
> I don't recall ever running into this before.
Which host are you pilling from? I am slurping things out of
c
Correct me if I am wrong, but I don't think you actually have to
disassociate any dev_t's from the driver (by clearing the si_drv[12]
fields) because we call destroy_dev and cdevsw_remove, so any later uses
of dev_t's get an error because the device has gone away.
Apart from that I don't think w
se the error is also present in netinet6/ipsec.c. There
> are some ifdef's around it that point to LINT needing some extra options.
>
> On Sun, 7 May 2000, Nick Hibma wrote:
>
> >
> > Is it only me that ever compiles LINT? The checksum changes went in a
> > few da
Is it only me that ever compiles LINT? The checksum changes went in a
few days ago.
Please, people, when you move code around or change a function that is
used in more than a fixed set of files, compile LINT. If unsure, compile
LINT. It's an extra five minutes, but well worth it.
linking kernel
You seem to have put in some hard work there. Yes, your analysis is
correct. the problem has been corrected not so long ago, albeit in a
slightly different way.
As it is now the ppi bus does not attach if the bus is polled mode. But
you are saying it works in polled mode as well.
I've attached
No, could you add
options DDB
makeoptions DEBUG=-g
to your kernel config and compile again? And reboot?
When the kernel panics it will end up in the kernel debugger. When that
happens, please write down the function names it comes up with.
if there is a function ca
Arg. What I really wanted to say was:
When it drops into the debugger, type 'trace' without quotes.
*sigh*
/me wanders off in search for a brain
On Fri, 5 May 2000, Nick Hibma wrote:
>
> No, could you add
>
> options DDB
> makeoptions DEB
Could you compile a debugging kernel with the kernel debugger included
and make it bomb again, and write down the function names that the trace
command on the DDB command line gives you and the exact trap message?
Thanks in advance.
Nik
On Fri, 28 Apr 2000, Leif Neland wrote:
> Sorry not to
The one directory I can remember that was missing from the acroread
file selector was a symbolic link (to the directory with the documents
I wanted of course :-). /usr/export was not found, but /usr/export/usb
was found when typed in in the top edit box.
> I see the same thing on 4.0-STABLE, so
> uhci0: port 0xe000-0xe01f irq 15 at device
>7.2 on pci0
> uhci0: LegSup = 0x0010
^^
PIRQDEN (IRQ's Enable) bit is not set by default. We set it right
afterwards, but you you might want to check this out by copying the
device_printf. The value should be 0x2000.
I
Could we stop this nonsense thread now? No one is against it. The only
reason why it is not in the tree is that no one has the time to actually
implement the change.
If someone wants it in the tree, do the work and submit it to the
current maintainer of Perl in FreeBSD.
Thanks in advance.
Nick
What does it say before this info? Shared interrupt?
USB does work on SMP (or at least in some cases).
> uhci_timeout: ii=0xc0a601c0
> uhci_timeout: ii=0xc0a601c0
> uhci_timeout: ii=0xc0a601c0
> usbd_new_device: addr=2, getting first desc failed
> uhub_explore: usb_new_device failed, error=TIME
> >- USB Keyboards
> >- Keyboard in DDB debugger does not work.
>
> In what configuration does it not work? I can use my USB keyboard in
> DDB without problems on a dual PPro box (4.0-STABLE) with a UHCI
> controller (VIA 83c572) card and a Pentium box (3.4-STABLE) with Intel
> PIIX3 here..
If've put up a list of things that need to be done still in the FreeBSD
USB stack. The list is _big_. I'll be adding things as they come up.
http://www.etla.net/~n_hibma/usb/usb.pl
A lot of the items are not that difficult to do and if you feel like
taking up a little project, start
You really want to look at other drivers, how they have been done. When
you are done, send me the diff and I will have a look at it.
It is fairly straightforward to convert from one to the other, once you
have understood both concepts a bit.
Nick
On Wed, 5 Apr 2000, Eric D. Futch wrote:
> I f
1 - 100 of 299 matches
Mail list logo
