> > it more difficult than I expected.
> > for one, the kernel date was missleading, the actual source update is the
> > key, so
> > the window of changes is now 28/July to 19/August. I have the diffs, but
> > nothing
> > yet seems relevant.
> >
> > on the other hand, I tried NFS/TCP, and there t
On Fri, 3 Oct 2008, Danny Braniss wrote:
it more difficult than I expected.
for one, the kernel date was missleading, the actual source update is the key,
so
the window of changes is now 28/July to 19/August. I have the diffs, but nothing
yet seems relevant.
on the other hand, I tried NFS/TCP
>
> On Fri, 3 Oct 2008, Danny Braniss wrote:
>
> >>> it more difficult than I expected.
> >>> for one, the kernel date was missleading, the actual source update is the
> >>> key, so
> >>> the window of changes is now 28/July to 19/August. I have the diffs, but
> >>> nothing
> >>> yet seems rele
On Fri, 3 Oct 2008, Danny Braniss wrote:
OK, so it looks like this was almost certainly the rwlock change. What
happens if you pretty much universally substitute the following in
udp_usrreq.c:
Currently Change to
- -
INP_RLOCK INP_WL
forget it about LOCK_PROFILING, I'm RTFM now :-)
though some hints on values might be helpful.
have a nice weekend,
danny
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, sen
On Fri, 3 Oct 2008, Danny Braniss wrote:
gladly, but have no idea how to do LOCK_PROFILING, so some pointers would be
helpfull.
The LOCK_PROFILING(9) man page isn't a bad starting point -- I find that the
defaults work fine most of the time, so just use them. Turn the enable syscl
on just
>
> On Fri, 3 Oct 2008, Danny Braniss wrote:
>
> >> OK, so it looks like this was almost certainly the rwlock change. What
> >> happens if you pretty much universally substitute the following in
> >> udp_usrreq.c:
> >>
> >> Currently Change to
> >> - -
> >> IN
Yes . my pci_probe is called for all the other bridge interfaces but its
not called for my PCI Card(Device ID and Vendor ID) instead of that Card
bus pci Probe is called while loading my driver as kldload.
I removed cbb driver out of kernel and tried. It works perfectly for me.
I think Class Type
Dear Baldwin,
Thanks for your support .but my pci probe function is not
getting called for my device id and vendor id. Because pccbb driver
already sets the device_set_desc as PCI-CardBus Bridge. So is there any
other option for me to make my_pciprobe function to be called for my
cor
Hello,
May be these are beginner questions ... could you plz answer the following
questions?
I think "options" line and "device" line are in the configuration file, in
order to support those features and devices. I see that sed script will
parse that file. Could you plz let me know what will be d
>
> On Fri, 3 Oct 2008, Danny Braniss wrote:
>
> > gladly, but have no idea how to do LOCK_PROFILING, so some pointers would
> > be
> > helpfull.
>
> The LOCK_PROFILING(9) man page isn't a bad starting point -- I find that the
> defaults work fine most of the time, so just use them. Turn the
On Fri, 3 Oct 2008, Danny Braniss wrote:
On Fri, 3 Oct 2008, Danny Braniss wrote:
gladly, but have no idea how to do LOCK_PROFILING, so some pointers would
be helpfull.
The LOCK_PROFILING(9) man page isn't a bad starting point -- I find that
the defaults work fine most of the time, so just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've just finished the first version of a Xorg driver for the UCLogic family of
graphic tablets. It may well work for other tablets, if I could see what folks
have, so I could program the names in.
Anyhow, the UCLogic tablets are *very* widely OEMed,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck Robey wrote:
> I've just finished the first version of a Xorg driver for the UCLogic family
> of
> graphic tablets. It may well work for other tablets, if I could see what
> folks
> have, so I could program the names in.
>
> Anyhow, the UCLog
On Oct 1, 2008, at 5:17 PM, John Baldwin wrote:
It sounds like you missed some of the dirhash changes somehow, as
dirhash no
longer has any lockmgr stuff in it (and only ever did in HEAD). I've
generated a patch though using svn. You can grab it from
http://www.FreeBSD.org/~jhb/patches/ufs_lo
>
> On Fri, 3 Oct 2008, Danny Braniss wrote:
>
> >> On Fri, 3 Oct 2008, Danny Braniss wrote:
> >>
> >>> gladly, but have no idea how to do LOCK_PROFILING, so some pointers would
> >>> be helpfull.
> >>
> >> The LOCK_PROFILING(9) man page isn't a bad starting point -- I find that
> >> the defaul
16 matches
Mail list logo
