Figured as much that is why I threw it in there.
Printable View
Is there still interest in trying to get some of the features working in a native Linux C program? I've had some experience with FTDI and other generic usbserial devices in linux, and I'd love to help you guys out.
I saw that WINE has done some more work with USB handling : http://wiki.winehq.org/USB
IBM did go to Mot. They wanted Mot to kick up the address space on the 6809 (like Intel did on the 8080) but Mot didn't figure there was enough volume in it to justify the R&D.
Very good read.Quote:
IBM's design was overly complex since they only had experience designing large grossly complex systems like the System 360 (has anyone read Fred Brooks' "The Mythical Man Month"... it's a good read)... so they ended up with the abomination they called the Personal Computer...
Actually, IBM was trying to clone the Apple ][. The first PC's had cassette storage, video like the Apple, etc.
Really!Quote:
Too bad IBM did not the have foresight to go with the 68000 (which had a true 32 bit architecture, unlike the 8/16 bit architecture of the 8088)... we're all paying for it now (and have been since day one).
Ah, too bad, looks like Motorola missed their greatest opportunity... just like DR with CP/M.
I didn't know IBM were trying to clone the Apple; it's funny, the INT13h cassette timer subcall is still present in some BIOS's, lol.
Yes, the 68000 internally was 32 bit even tho the external bus was 16 bit, it would do two bus cycles for an external 32 bit transfer.
On the other hand, the 8088/8086 internally were 16 bit, and used segment registers to manipulate the address range beyond 64K.
Heh. Online at the same time ... Yeah, Mot blew it big time on that one.
I can't remember where I learned that. Maybe Byte back in the day. I still have PC and AT manuals will full schematics and BIOS listings. That is where IBM blew it.Quote:
I didn't know IBM were trying to clone the Apple; it's funny, the INT13h cassette timer subcall is still present in some BIOS's, lol.
Yeah, I an no fan of the X86 architecture. Other than playing a bit with an 1802 and 6502, I used Mot on the desk and in product, from the 6800 to 68040 for my desktop/development and 6802 to 68340 in product. I had Mot based Ataris for a while. I developed a lot of code in the field on an ST or Falcon. I can write assembler for any of them, which is something I don't attempt on X86. I finally got an X86 box to run linux. It is a long way from assembler/editor off tape and code back to tape to 3GHz processors, C, 1TB drive, ....Quote:
Yes, the 68000 internally was 32 bit even tho the external bus was 16 bit, it would do two bus cycles for an external 32 bit transfer.
On the other hand, the 8088/8086 internally were 16 bit, and used segment registers to manipulate the address range beyond 64K.
Sometime I'd like to talk to you about git. I just got hosed by a CVS merge.
I use git every day... pm me your phone # and we can talk sometime tomorrow.
I am a linux dev
C / C++ / ASM
I run my own small business which I mostly use GCC
how about you?
Do you think you can get a hook working for the USB so we can use EFILive to flash in Linux finally?
Haven't tried in a long time, might see if it is possible now, openSUSE my mainstay has an emulator for Winders, going to try it out this time.
Anyone tried running it under wine?
What info do you need to try and get it working on Linux?
Regards
Paul
I don't think that is what they meant, the discussion about getting Linux playing with EFILive nicely.
I'm not a Linux desktop user so you guys will have to educate me on this, but with the insane amount of Linux Distros if you get it working on one will it work on all the others?
Right but the comp in my computer is linux. I can help with the dev of the usb stuff but that is something that I have been after for many years. It sucks not knowing trans temp
It should be the same info to make a Windows driver; We need to know how to talk to the hardware (hardware protocol). Then, once we can talk to the hardware, we need to know what to say to make it do it's thing. I realize the latter part is actually done from the userland app, but that info is needed for driver devel purposes in order to verify that it actually works :)
As a rule, there are two main distros that everyone supports: Fedora/Red Hat, and Ubuntu/Debian. Most other distros are built off of those. For the distros that don't meet their dependency requirements we can also make the source available for the user to compile themselves (which means they have to take care of all the dependencies).
The kernel module would likely be done as a dynamically built module, much like VirtualBox does. Here, the install script compiles a kernel module against the running kernel at install time, and installs kmod as a dependency. kmod ensures that if a future system update installs a new kernel version, a new module will be built against the new kernel at the first boot of the new kernel. If the module is stable (which requires the Flashscan V2 hardware protocol to be stable) and licensed under GPLv2 it may be possible to get it put into the mainline kernel tree. If that happens, then a module build would no longer be required for any distros that are based on a kernel version the same or newer than the version where the driver was introduced into the tree.
Are you thoroughly confused yet?
You need the send and receive signal converted to an output.
Right .deb and .rpm covers most Linux Distros. Out of the top 5 Distors, 3 are .deb and the other are .rpm, according to Distrowatch.com.
I like the idea of not having to run in Wine as MaxPF is alluding to.
Man a Raspberry PI a few tweaks and a small EFILive device could be born, no, laptop of tablet needed. https://www.google.com/search?q=raspberry+pi&ie=utf-8&oe=utf-8
Do you have the factory Service Manual, does it show a resistance or voltage to temperature chart...?
The GM SM's show the resistance to temperature charts, so by looking at the wiring diagram it is easy to come up with a voltage->temperature formula.
I am not familiar with Cummins/Dodge stuff at all.
Anyone try any more, my com crashed and just now got one back up and going.
Got another lappy on the way, but it will have Winders 10 on it, YUCK! Well not for long.
If you can, go back to Win 7 or Win 8.
I just installed openSUSE 42.1 and left the Winders 10 as it is, if EFILive were Linux friendly I would never use Winders again.
Lenovo packs their laptops with lots of bloatware, and Winders 10, WTF, used it (W10) for a few days just so I can say I have used it, got a virus attack the last day before installing Linux, no more worries now.