Hoi Eric 😊

This is my list of the DELL inspire 1525 with pcisleep

This is PCISLEEP by Eric Auer 12mar2005 - Free open source software.
Read GNU General Public License 2 at www.gnu.org

PCI BIOS version 2.10, highest bus number is 13.
Interfaces: 10 is OHCI for USB/FireWire, 20 is EHCI for USB 2.0, etc.
Bridges: 'from bus X to Y (subordinate Z)' shown as '[XX->YY(ZZ)]'
Power Management support shown as: D1 idle, D2 halt, D3 soft-off

bus.device(.function) [vendor:model] classcode(/iface) vendor class [details]
BusDevF  vend:type  class   vendor     description...
00.00   [8086:2a00] 0600    Intel      CPU host bridge
00.02.0 [8086:2a02] 0300    Intel      VGA graphics [D3]
00.02.1 [8086:2a03] 0380    Intel      graphics unit [D3]
00.1a.0 [8086:2834] 0c03    Intel      USB controller
00.1a.1 [8086:2835] 0c03    Intel      USB controller
00.1a.7 [8086:283a] 0c03/20 Intel      USB controller [D3]
00.1b   [8086:284b] 0403    Intel      multimedia [D3]
00.1c.0 [8086:283f] 0604    Intel      PCI bridge [00->09]
00.1c.1 [8086:2841] 0604    Intel      PCI bridge [00->0b]
00.1c.4 [8086:2847] 0604    Intel      PCI bridge [00->0c(0d)]
00.1d.0 [8086:2830] 0c03    Intel      USB controller
00.1d.1 [8086:2831] 0c03    Intel      USB controller
00.1d.2 [8086:2832] 0c03    Intel      USB controller
00.1d.7 [8086:2836] 0c03/20 Intel      USB controller [D3]
00.1e   [8086:2448] 0604/01 Intel      PCI bridge [00->02]
00.1f.0 [8086:2815] 0601    Intel      ISA bridge
00.1f.1 [8086:2850] 0101/8a Intel      IDE controller
00.1f.2 [8086:2829] 0106/01 Intel      storage (disk) [D3]
00.1f.3 [8086:283e] 0c05    Intel      SMBus controller
02.09.0 [1180:0832] 0c00/10 other      FireWire IEEE1394 [D1,D3]
02.09.1 [1180:0822] 0805/01 other      PC system device [D1,D3]
02.09.2 [1180:0843] 0880    other      PC system device [D1,D3]
02.09.3 [1180:0592] 0880    other      PC system device [D1,D3]
02.09.4 [1180:0852] 0880    other      PC system device [D1,D3]
09.00   [11ab:4354] 0200    other      LAN / Ethernet [D1,D3]
0b.00   [14e4:4315] 0280    Broadcom   network (WLAN?) [D1,D3]
PCI bus scan done.

Also other software recognized the lan card as  a Yukodi LAN adapter from 
Marvell.

Any other tools/utilities I can use?

Regards
Nico

-----Original Message-----
From: Eric Auer via Freedos-user <freedos-user@lists.sourceforge.net> 
Sent: Sunday, July 28, 2024 10:52 PM
To: Discussion and general questions about FreeDOS. 
<freedos-user@lists.sourceforge.net>
Cc: Eric Auer <e.a...@jpberlin.de>
Subject: Re: [Freedos-user] Printing to USB Printers


Hoi Nico,

bedankt voor je uitleg!

> To clarify
> A) It is an epson printer. With a centronics parallel interface
> B) I have a usb to centronics cable wich works ( under windows 10)
> C) The cable interface uses a ch341a chip.

My guess is that this should not matter: There should be a generic category of 
USB printer ports supported by the cable. But we have actual USB experts here 
who may either confirm that intuition or say that I am totally wrong :-)

https://www.usb.org/sites/default/files/usbprint11a021811.pdf

> D) i dont have an ethernet (wired) connection yet with the laptop.

Which chipset does the laptop use for wired networking?
You can use PCISLEEP to check which devices you have.

> E) DosUsb gives Errors when talking tot the printer.

Sounds like a question for the USB expert(s) here!

> My thoughts were to build a driver to talk to the ch341a in c or 
> assembly. To be continued

You do not want  to do that from scratch. For USB, there is a big mountain of 
stacked layers of logical structure and in operating systems with versatile USB 
support, you would only have a driver for the chip in context of all the 
already existing drivers for USB in general, which in turn support USB 
controllers on your mainboard in somewhat generic ways, to need less instance 
specific complexity.

So what you would do in DOS is: Wonder whether the generic USB driver can treat 
the chip as instance of a generic USB printer port category and if not, whether 
you can get it supported by making it a special case of it with as small as 
possible differences, to not have to modify too much in the USB drivers.

A driver "only for the chip" would not help you, as the chip always exists in 
some large, complex USB ecosystem.

Regards, Eric




_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user



_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to