backs. Is it possible? Or should I make N pairs
of almost-the-same thunk functions?
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail
ot;uXXXcom"
(b) Driver instances looks ugly (like "mos78400")
Is "umos7840com" good name or it is too long? :) We have "umoscom"
driver for older MosChip chip in base already.
--
// Black Lion AKA Lev Serebryakov
_
doesn't help much.
> Are you sure?
> The last two arguments to DRIVER_MODULE() look like what you want.
Yes, it my fault, it works after hint from Hans Petter Selasky.
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org
Hello, Paul.
You wrote 19 ноября 2010 г., 19:56:26:
> Is it possible/sane to integrate two drivers in one?
No, they are almost totally different.
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
h
eg: cyl 0/ head 130/ sector 3;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
The data for partition 3 is:
The data for partition 4 is:
blob#
What should I do to mount this card?!
--
// Black Lion AKA Lev Serebryakov
2) WHY, OR WHY old module was loaded without problems?! ABI is
broken (ucom_detach()? size of struct ucom_softc) and old module
should complain on load, IMHO! Users will be very surprised when
computer will reboot after system update!
--
// Black
ecked
appropriate HEAD commits).
Other problem is, that old modules still can be loaded in new kernel,
and AFAIK, here is some mechanism to prevent it, like OSVERSION too.
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
ht
#x27;ve tried to make code style(9) compatible too, but I will not swear,
that it 100% style(9)-proof :)
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
about these options
(man 8 blazer).
#
I'm posting it here, but not to NUT mailing list, because it seems,
that blazer_usb will need HID device, and FreeBSD doesn't detect one.
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org
ttached to another port. Is
here any method to set owner:group of device node by VID/PID or ID
string or something like this?
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freeb
but it is only "symbolic link"
and real device is "/dev/usb/1.2.0" in such case -- as result, owner
and permissions on real device stay unchanged and "blazer_usb" can not
access it again :(
--
// Black Lion AKA Lev Serebryakov
_
as I understand, old-framework based driver is not actual
for -CURRENT, and I need to provide version for new framework too.
Is here any documentation on new (and old, to be honest) USB
framework API?
http://wiki.freebsd.org/USB doesn't give any useful information for
developer.
--
// Black Li
ver with my device.
> Is your device multi port or single port?
4 ports.
> It should be quite trivial to make a device driver for a serial port device.
Yep, cleanup of existing "driver" (it was ugly) was
straightforward. This provided "driver" can't even send
re not complete, and some
registers are left in driver as `magic' numbers. I don't like it, but
Moschip doesn't answer on e-mails :(
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman
f existing "driver" (it was ugly) was
straightforward. This provided "driver" can't even send BREAK signal :)
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
Hello, Freebsd-usb.
Some software (with Linux origins, of course), which I want to port,
uses libusb1 (libusb-1.0). Is it availiable on FreeBSD? It seems, that
`ports/devel/libusb' is something very different...
--
// Black Lion AKA Lev Serebr
s not yet supported. ports/devel/libusb gives you libusb 0.1
Any ongoing project of porting?
> (will be part of the base OS in 8.0).
According to USBTODO wikipage, here is plan to add 1.0 support to
8.0?
--
// Black Lion AKA Lev Serebryakov
__
Hello, Freebsd-usb.
Does FreeBSD supports CDC/RNDIS devices?
Will USB device, which works on Windows and MacOS X "without drivers"
(with standard, generic drivers, provided by OS) work on FreeBSD?
--
// Black Lion AKA Lev Serebryakov
_
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
e, local USB Guru Hans Petter Selasky could give cime advicec how to
debug this situation. I've added freebsd-usb@ to CC:
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
as my first thought: ``I forget to disable internal interrupts on device
close''), so, theoretically, it should stop spam system with interrupts...
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
http://list
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Hello, Harald.
You wrote 17 сентября 2013 г., 12:46:25:
HS> The Y is the device addr @ bus #X.
Oh :)
HS> Same posted some seconds ago :-)
Yep, exactly the same pattern.
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org m
ich is total
bullshit) doesn't say anything about configuring these buffers.
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
I'll take a look at USB
audio.
--
// Black Lion AKA Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
art to write new one -- I needed
BREAK to enter kernel debugger).
HS> At least, it seems to be possible to enable RS485-mode :-) :-)
I could easily add RS485 mode, BUT! FreeBSD doesn;'t have any userland API
for it, and the same is true for higher and non-standard baud rates.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Is here practical buffer size limit? I mean, maybe, standard limits
transfer size by 64K or something like this?
- --
// Lev Serebryakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32
sing an
> internal buffer, unlike Linux. You should be able to setup any
> positive length which fits into an integer of type "int" or
> "uint32_t".
My question is more about cross-platform behavior, as I try to write
cross-platform project.
- --
// Lev Serebryakov
-
e for only $150, which uses UASP to attach to
host computer. It could be nice addition to FreeBSD-based storage servers.
--
// Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, s
is
SCSI at its core, so sit should be new transport layer for CAM?
> In USB 2.0 mode it will work using BULK only. Not sure if the vendors
> provide BULK only configurations for USB 3.0.
Attach 5 disks via one USB2 links is not good idea anyway
kov.spb.ru 12.0-CURRENT FreeBSD
12.0-CURRENT #0 r318590M: Sun May 21 15:26:16 MSK 2017
But 11.0-CURRENT (year old, before release) showed same behavior.
--
// Lev Serebryakov
signature.asc
Description: OpenPGP digital signature
15:21:13.917161 usbus1.2 SUBM-CTRL-EP=0080,SPD=LOW,NFR=2,SLEN=8,IVAL=0
15:21:13.920128 usbus1.2
DONE-CTRL-EP=0080,SPD=LOW,NFR=2,SLEN=4,IVAL=0,ERR=0
--
// Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/
t out you'll need to enable
> debugging in the UPS software package.
If UPS software is not running, flickering is the same. It doesn't
depend on running of UPS software (sysutils/nut, nothing fancy or
closed-sourced).
--
// Lev Serebryakov
signature.asc
Description: OpenPGP digital signature
to fix on FreeBSD!
--
// Lev Serebryakov
signature.asc
Description: OpenPGP digital signature
such devices).
I know next to nothing about Linux and USB internals, but I'm ready to
test patches, get any dumps, try to boot Linux on this hardware and get
dumps there, etc.
Thank you!
--
// Lev Serebryakov
signature.asc
Description: OpenPGP digital signature
RE),
But this product have "generic" id 0x. Maybe, it should be added to
quirks table too? Or "import" this table:
https://fossies.org/linux/nut/scripts/hotplug/libhid.usermap
I'll try Linux in next several days.
--
// Lev Serebryakov
signature.asc
Description: OpenPGP digital signature
connected to Windows notebook. Yes, I understand, that it
is different host hardware.
Unfortunately, I can not check other OSes on hardware where it flickers, but
maybe it is possible to set (or add) some quirk on our side?
--
// Lev Serebryakov
signature.asc
Description: OpenPGP digital
sable_enumeration=1
>
> Does your device still function?
Nope, it still disappears. Looks like I need to boot this computer with Linux
and check in Linux. Problem is, it is system with serial console only and I
don't know Linux Live CD/USB Image where serial console is enabled and wh
s enabled and
>> which doesn't require screen & keyboard.
>
> LOW speed USB is a bit special.
>
> Try this also:
>
> usbconfig -d X.Y power_save
>
> While the device is attached.
No effect at all...
--
// Lev Serebryakov
signature.asc
Description: OpenPGP digital signature
.ucom.pps_mode: 0
hw.usb.uftdi.skip_jtag_interfaces: 1
hw.usb.full_ddesc: 0
hw.usb.no_cs_fail: 0
hw.usb.disable_port_power: 0
hw.usb.disable_enumeration: 0
hw.usb.power_timeout: 30
hw.usb.usb_lang_mask: 255
hw.usb.usb_lang_id: 9
hw.usb.template: -1
hw.usb.debug: 0
hw.usb.no_shutdown_wait: 0
s: port 2,
wPortStatus=0x0100, wPortChange=0x0003, err=USB_ERR_NORMAL_COMPLETION
Apr 17 21:31:49 gateway kernel: uhub_reattach_port: reattaching port 2
Apr 17 21:31:49 gateway kernel: ugen2.2: at usbus2
(disconnected)
--
// Lev Serebryakov
signature.asc
Description: OpenPGP digital signature
reporting are
different for different NKRO keyboards.
You could read more here: https://www.devever.net/~hl/usbnkro
Looks like, FreeBSD HID/kbd driver has problem with "bitmap" reporting and
this keyboard switch to NKRO mode after boot regardless.
I've CC: this message to usb@ mailing list, as it looks like USB problem on
FreeBSD side, in HID driver.
--
// Lev Serebryakov
signature.asc
Description: OpenPGP digital signature
0 notebook,
that it doesn't disconnect from Windows host.
And it flicker on FreeBSD systems.
Looks like, we need some quirk for this class of devices.
I could collect logs on FreeBSD and Windows, but I don't know what to compare
and where to look.
-
11 on same Laptop as I have
Windows 10 installed . I'll try it ASAP.
--
// Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
ot; system: flicker
connect/disconnect forever.
But it is not same hardware, as Windows 10, as my Windows 10 Laptop silently
refuse to boot from USB stick :-(
--
// Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailma
hci.debug=17
hw.usb.ohci.debug=17
Need debug support (unknown oid 'hw.usb.xhci.debug'). Looks like I need "test"
laptop with debug kernel. I'll do it and report back.
--
// Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
https
md=HOST spd=LOW (1.5Mbps) pwr=ON
(100mA)
Can you enable host controller debugging:
hw.usb.xhci.debug=17
hw.usb.ehci.debug=17
hw.usb.uhci.debug=17
hw.usb.ohci.debug=17
900Kb of dump from first connect to last disconnect is here:
http://lev.serebryakov.spb.ru/_sklad/ups-flickr-one-cycle.tx
ovided" software (very crude one) works and shows
plausible information.
Windows 10 shows it as "HID UPS Battery" in device manager.
--
// Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
d re-attech in the loop.
(4) FreeBSD WITH nut: try to catch this combination, but it is not-trivial and
fragile, not usable in production now, as UPS have detached itself before nut
could start typically.
--
// Lev Serebryakov
___
freebsd-usb@f
xt
Looks like, I need small kernel-level driver which "prime" HID UPSes on
connect with pre-canned requests to stop them from disconnect.
--
// Lev Serebryakov
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/lis
50 matches
Mail list logo
