Re: Bug#560088: ITP: python-portio -- low level port I/O for Linux
Ron Johnson, le Wed 09 Dec 2009 01:28:26 -0600, a écrit : On 2009-12-08 17:42, Dmitrijs Ledkovs wrote: 2009/12/8 Ben Hutchings b...@decadent.org.uk: I'm working on a parallel LCD interface with my custom PCB and I wanted interactive way to use parallel port. Found this decided to package it for myself and anyone else. Why using that when you have all ioctls to do the same portably in linux/ppdev.h ? Samuel -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#560088: ITP: python-portio -- low level port I/O for Linux
On Tue, Dec 08, 2009 at 08:23:15PM +, Dmitrijs Ledkovs wrote: * Package name: python-portio Version : 0.4 Upstream Author : Fabrizio Pollastri f.pollas...@inrim.it * URL : http://portio.inrim.it/ * License : GPL-3+ Programming Lang: Python, C Description : low level port I/O for Linux Wrapper for the port I/O macros like outb, inb and other provided by the C library on Linux x86 platforms. Honestly, this doesn't sound like something that should be encouraged. inb and outb are the source of much incompatibility between architectures, and any package depending on this one will be (likely permanently) stuck to i386. Is there something that you want to package that depends on this? -- brian m. carlson / brian with sandals: Houston, Texas, US +1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Re: Bug#560088: ITP: python-portio -- low level port I/O for Linux
On Tue, 2009-12-08 at 22:37 +, brian m. carlson wrote: On Tue, Dec 08, 2009 at 08:23:15PM +, Dmitrijs Ledkovs wrote: * Package name: python-portio Version : 0.4 Upstream Author : Fabrizio Pollastri f.pollas...@inrim.it * URL : http://portio.inrim.it/ * License : GPL-3+ Programming Lang: Python, C Description : low level port I/O for Linux Wrapper for the port I/O macros like outb, inb and other provided by the C library on Linux x86 platforms. Honestly, this doesn't sound like something that should be encouraged. inb and outb are the source of much incompatibility between architectures, and any package depending on this one will be (likely permanently) stuck to i386. They're not really the source of much incompatibility, because people rarely try to use them! I have written a module like this myself for testing some new hardware. On top of the low-level I/O, I defined classes for PCI devices and register sets, and then wrote test cases using them. It was a lot easier to write those test cases in Python than it would have been in C. Is there something that you want to package that depends on this? I do hope not; this should never be used in production. But it may yet be useful in hardware development. Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky signature.asc Description: This is a digitally signed message part
Re: Bug#560088: ITP: python-portio -- low level port I/O for Linux
2009/12/8 Ben Hutchings b...@decadent.org.uk: I do hope not; this should never be used in production. But it may yet be useful in hardware development. Ben. I'm working on a parallel LCD interface with my custom PCB and I wanted interactive way to use parallel port. Found this decided to package it for myself and anyone else. Should my packaging be changed to i386 amd64 only? -- With best regards Dmitrijs Ledkovs (for short Dima), Ледков Дмитрий Юрьевич () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#560088: ITP: python-portio -- low level port I/O for Linux
On 2009-12-08 17:42, Dmitrijs Ledkovs wrote: 2009/12/8 Ben Hutchings b...@decadent.org.uk: I do hope not; this should never be used in production. But it may yet be useful in hardware development. Ben. I'm working on a parallel LCD interface with my custom PCB and I wanted interactive way to use parallel port. Found this decided to package it for myself and anyone else. Should my packaging be changed to i386 amd64 only? If libc provides these functions on every platform, then I'd say, no! OTOH, you might want to add to the Long Description a disclaimer mentioning possible cross-platform compatibility issues. -- scientia addo vereor -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
