Menu
▾
▴
tilp-devel — This list is intended to TiLP's developers, contributors and advanced users.
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
(2) |
Dec
(2) |
| 2003 |
Jan
(25) |
Feb
(5) |
Mar
(12) |
Apr
(46) |
May
(47) |
Jun
|
Jul
(2) |
Aug
|
Sep
(15) |
Oct
(8) |
Nov
(11) |
Dec
|
| 2004 |
Jan
(25) |
Feb
(24) |
Mar
(13) |
Apr
(59) |
May
(52) |
Jun
(6) |
Jul
(3) |
Aug
(7) |
Sep
(33) |
Oct
(17) |
Nov
(16) |
Dec
(1) |
| 2005 |
Jan
(4) |
Feb
|
Mar
(2) |
Apr
(5) |
May
(50) |
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
(7) |
Oct
(1) |
Nov
(2) |
Dec
(9) |
| 2006 |
Jan
(10) |
Feb
(6) |
Mar
(2) |
Apr
(24) |
May
(32) |
Jun
(53) |
Jul
(26) |
Aug
(28) |
Sep
(59) |
Oct
(72) |
Nov
(85) |
Dec
(57) |
| 2007 |
Jan
(43) |
Feb
(26) |
Mar
(25) |
Apr
(36) |
May
(13) |
Jun
(14) |
Jul
(53) |
Aug
(68) |
Sep
(46) |
Oct
(62) |
Nov
(15) |
Dec
(4) |
| 2008 |
Jan
(4) |
Feb
(5) |
Mar
(7) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
(5) |
Nov
|
Dec
(3) |
| 2009 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Romain <ro...@li...> - 2006-10-12 21:30:57
|
Hi, > <<E008 is the 84P SE. E003 is the 84P.>> Maybe, I should add E003 but I can't test it. In fact, I have never seen any 84P with USB. roms. > > http://wikiti.denglend.net/index.php?title=3D83Plus:OS:84_Plus_USB_Info= rmation#In_Other_News > > -- Olivier Armand > > -----------------------------------------------------------------------= -- > Using Tomcat but need to do more? Need to support web services, securit= y? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron= imo > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ > TiLP-devel mailing list > TiL...@li... > https://lists.sourceforge.net/lists/listinfo/tilp-devel > --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Romain <ro...@li...> - 2006-10-12 21:29:31
|
Hi, currently, the following IDs are listed in TI's USB driver: %DESCRIPTION%=3DDriverInstall,USB\VID_0451&PID_E003 %DESCRIPTION%=3DDriverInstall,USB\VID_0451&PID_E004 %DESCRIPTION%=3DDriverInstall,USB\VID_0451&PID_E008 %DESCRIPTION%=3DDriverInstall,USB\VID_0451&PID_E009 %DESCRIPTION%=3DDriverInstall,USB\VID_0451&PID_E00A %DESCRIPTION%=3DDriverInstall,USB\VID_0451&PID_E00B %DESCRIPTION%=3DDriverInstall,USB\VID_0451&PID_E00C %DESCRIPTION%=3DDriverInstall,USB\VID_0451&PID_E00D roms. --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Terry M. <il...@ce...> - 2006-10-12 20:38:07
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <img alt="" src="cid:par...@ce..." height="381" width="760"><br> If you have trouble playing quickly after a few weeks of this practice, be sure you are not moving your tongue over a greater distance than necessary. I'd be happy to leave my job if it meant we could be together.<br> To do this I place the mouthpiece slightly off-center on my chops, then I can force this to happen.<br> I used to work with a French horn player who had to clean his mouthpiece every day with alchohol - otherwise he would develop sores on his lips. I have also found it really valuable when I am moving across certain notes within the triplet. Gradually move it to higher and lower notes.<br> If it is a vinyl case, you should clean the inside of the case as well.<br> This produces the intended pitch plus a softer note one octave lower. com publishes Going Mobile With SVG: Standards by Antoine Quint.<br> Read more in the ZOOMON Press Release. If your moutpiece is not clean it can also cause some pesty infections or rashes around the mouth.<br> I'd be happy to leave my job if it meant we could be together.<br> Read more in Antoine Quint's weblog. This used to happen to me in college marching band when I was really tired.<br> This site probably has a calculator already set up to do the math for you.<br> The notes came out much more clearly with the alternate pattern. Even if you do this studiously, once you are playing in an ensemble or practicing a difficult etude, the stresses may cause the extra pitches to return now and then. An evaluation version is available for download. Then during your warm-up, start out in a very comfortable range and gradually work toward higher and lower notes. Results of some recent are also available so you can see how prices range.<br> It converts PDF to SVG; both GUI and command line converters are available.<br> This is a great march for low brass players, with great bass lines and a lovely euphonium counter melody.<br> This is a great march for low brass players, with great bass lines and a lovely euphonium counter melody.<br> Requires free registration. Regular cleaning with soap and water will probably be sufficient in most cases. The software runs in a .<br> I got caught up with them once before and had trouble then.<br> I have also found it really valuable when I am moving across certain notes within the triplet. It integrates the Batik toolkit to enable SVG generation.<br> Requires free registration. Start at a medium volume, then do a little work at softer volumes, then at louder volumes.<br> Most people focus on making the ku sound clean, and that is important. Read more in Antoine Quint's weblog. The notes came out much more clearly with the alternate pattern.<br> The triband GSM, GPRS phone is available in the European, Asia-Pacific, and Latin American markets. Read more in Antoine Quint's weblog. com publishes Going Mobile With SVG: Standards by Antoine Quint.<br> <br> </body> </html> |
|
From: Olivier A. <oli...@gm...> - 2006-10-12 19:14:08
|
Hi, > > Finally, a question, does the vanilla TI84+ work? Because according to > > Yes, it does. > > > wikiti its USB product ID is E003, which is nowhere to be found in the > > source code. > > its produt ID is E008 (defined in ticables.h). According to Dan Englender: <<E008 is the 84P SE. E003 is the 84P.>> http://wikiti.denglend.net/index.php?title=83Plus:OS:84_Plus_USB_Information#In_Other_News -- Olivier Armand |
|
From: Romain <ro...@li...> - 2006-10-12 14:16:38
|
Hi Tijl, > * I moved the call to usb_init() from linux/link_slv.c:tigl_enum() to > ticables.c:ticables_library_init(). This function should only be > called once and so ticables_library_init() is really the best place > for it. Romain you should check if I got the ifdef correct. There > should perhaps be NO_CABLE_SLV in there as well. that's ok for me. You're right. > * In linux/link_slv.c I disabled the use of tigl_get_product(). This > function is giving problems somehow, but I'm not entirely sure why. Which kind of problems? > It would be interesting to know if this solves the Linux TI89ti > problems too, which is why I committed it, since this is sure to be > a temporary solution. I will try and compile it. > Finally, a question, does the vanilla TI84+ work? Because according to Yes, it does. > wikiti its USB product ID is E003, which is nowhere to be found in the > source code. its produt ID is E008 (defined in ticables.h). thx, roms. --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Tijl C. <ti...@ul...> - 2006-10-12 13:33:00
|
On Wednesday 11 October 2006 22:40, Tijl Coosemans wrote: > Today I finally managed to spend some time on TiLP and got my > silverlink working. I'll clean up my changes and commit them some > time tomorrow hopefully. I've committed a couple things. Most are *BSD specific, but the following is global: * I moved the call to usb_init() from linux/link_slv.c:tigl_enum() to ticables.c:ticables_library_init(). This function should only be called once and so ticables_library_init() is really the best place for it. Romain you should check if I got the ifdef correct. There should perhaps be NO_CABLE_SLV in there as well. * In linux/link_slv.c I disabled the use of tigl_get_product(). This function is giving problems somehow, but I'm not entirely sure why. It would be interesting to know if this solves the Linux TI89ti problems too, which is why I committed it, since this is sure to be a temporary solution. Finally, a question, does the vanilla TI84+ work? Because according to wikiti its USB product ID is E003, which is nowhere to be found in the source code. > I have another problem though. TiLP segfaults whenever I select > "Change device" from the popup menu (or hit Ctrl+D). It does work > when there's no ".tilp" in my home directory. Is this known or > FreeBSD only? No fix for this yet... |
|
From: Romain <ro...@li...> - 2006-10-12 09:48:40
|
Hi, > Today I finally managed to spend some time on TiLP and got my > silverlink working. I'll clean up my changes and commit them some time > tomorrow hopefully. wonderful! > I have another problem though. TiLP segfaults whenever I select "Change > device" from the popup menu (or hit Ctrl+D). It does work when there's > no ".tilp" in my home directory. Is this known or FreeBSD only? it appeared on WinMe... > > -----------------------------------------------------------------------= -- > Using Tomcat but need to do more? Need to support web services, securit= y? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron= imo > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ > TiLP-devel mailing list > TiL...@li... > https://lists.sourceforge.net/lists/listinfo/tilp-devel > thx, roms. --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Elmer E. <nu...@uo...> - 2006-10-12 08:51:32
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <img alt="" src="cid:par...@uo..." height="321" width="598"><br> "The United States will use this sentence to pressure Saddam to save it from its mess.<br> Let's hope the EMP talk is just idle gossip on the jihadi grapevine.<br> I believe their indoctrination far exceeds that of the Nazis.<br> The film touches on the eery correlation between Nazi propaganda and radical Islamic propaganda. As you state in your blogs, things are fronts.<br> We did not connect dots. He said they had fought recently in Afghanistan.<br> The sick and reprehensible nature of something like that is just bewildering.<br> The Ahmadiyya Center of Detroit is set on fire shortly afterward. The sick and reprehensible nature of something like that is just bewildering.<br> He said they had fought recently in Afghanistan. it will blow like a volcano. William Cain, an Al-Fuqra follower from Akron, Ohio was identified as Ahmad's murderer.<br> As has correctly been noted in the news, the Islamofascist threat does not stem from one group, but from many groups who share common inspiration, common goals, and common connections. Three pipe bombs were placed in a room on the fourth floor of the hotel by Stephen Paster, who is said to be one of the organizers of Al-Fuqra in the United States.<br> Cold, calculating, and covert, they plotted and planned attack after attack.<br> And so, we have found ourselves seeking out foreign terrorists that are plotting and planning, yet left vulnerable to "fellow Americans" with a knife in our back.<br> Turabi was an ally of Saddam Hussein and is a long-time friend and benefactor of Osama bin Laden. He said they had fought recently in Afghanistan.<br> marshals and charged with smuggling guns between South Carolina and New York. Hen then travels to Lahore, Pakistan and declares his allegiance to Shiekh Gilani. William Cain, an Al-Fuqra follower from Akron, Ohio was identified as Ahmad's murderer. If so, feel free to take them out.<br> He served just four years and then moved to Pakistan. If so, feel free to take them out. We are indeed involved in much wider war than many realize. They had applied for several million more after inflating their enrollment numbers. This very summer, members of this group from all over the country will converge at the rural headquarters in upstate New York for their annual training retreat.<br> It's time to deal with them. Did you know that the Grand Mufti of Jerusalem met with Hitler and even raised up a Bosnian Muslim division of SS Panzer troops? The existence of a connection is still unclear.<br> One Mohammad Gilani, a general in the communist-era military, served as chief of the Taliban air force.<br> After the withdrawal of the Soviet troops, they spread to other countries in the Islamic as well as the non-Islamic world and created havoc through acts of terrorism.<br> The memo says the officers' actions were based on "irrational fears". Cold, calculating, and covert, they plotted and planned attack after attack. There, he reportedly trained jihadis in bombmaking in cooperation with the ISI. As you state in your blogs, things are fronts.<br> Gilanis are well known in Afghani regions as well.<br> <br> </body> </html> |
|
From: Tijl C. <ti...@ul...> - 2006-10-11 20:41:17
|
On Thursday 05 October 2006 13:14, Romain Li=E9vin wrote: > > I don't have an 84 or 89t, but I'll have a look at it. >=20 > If SilverLink cable is working under BSD then DirectLink should, too. > Clearly, you can easily assume that 84+/89t is working if SilverLink > is working (but I have a counter-example with Titanium/USB under > Linux :-( Today I finally managed to spend some time on TiLP and got my silverlink working. I'll clean up my changes and commit them some time tomorrow hopefully. I have another problem though. TiLP segfaults whenever I select "Change device" from the popup menu (or hit Ctrl+D). It does work when there's no ".tilp" in my home directory. Is this known or FreeBSD only? |
|
From: Romain <ro...@li...> - 2006-10-05 13:02:21
|
Hi, > Can you upload the libti* and tilp src tarballs to sf.net for us > packagers? Done. roms. > > -----------------------------------------------------------------------= -- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > TiLP-devel mailing list > TiL...@li... > https://lists.sourceforge.net/lists/listinfo/tilp-devel > --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Romain <ro...@li...> - 2006-10-05 11:15:06
|
Hi, > Can you upload the libti* and tilp src tarballs to sf.net for us > packagers? Yes, I can. It will be done on today... roms. --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Romain <ro...@li...> - 2006-10-05 11:14:32
|
Hi, >> 3. Similarly to (2), all "cuaa"s in src/bsd/link_gry.c have to be >> changed to "cuad"s. > > This isn't entirely correct. The name has only been changed since > FreeBSD 6. Everything before that still uses cuaaX. Err... Maybe it should be probed by detect.c or in the link_xxx.c file. > I don't have an 84 or 89t, but I'll have a look at it. If SilverLink cable is working under BSD then DirectLink should, too. Clearly, you can easily assume that 84+/89t is working if SilverLink is working (but I have a counter-example with Titanium/USB under Linux :-( Thanks to you Tijl, roms --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Tijl C. <ti...@ul...> - 2006-10-05 10:54:01
|
On Wednesday 04 October 2006 13:39, Romain Li=E9vin wrote: > This is an issue you will have to take a look because I don't have > any *BSD system. Maybe, you should attempt to mail Tijl Coosemans > which was the original author of the BSD code. Can you upload the libti* and tilp src tarballs to sf.net for us packagers? |
|
From: Tijl C. <ti...@ul...> - 2006-10-05 10:06:59
|
On Monday 02 October 2006 12:20, Sean McLaughlin wrote:
> Well, I managed to get TiLP-II to compile and run moderately
> successfully on FreeBSD, but there were some issues:
Thanks, that means less work for me :)
> 1. src/bsd/detect.c #include's "stdints.h", which doesn't exist.
> I had to pull in the one from the previous version.
This has already been fixed apparently. Maybe the entire dir needs to
be resynced with the Linux code. I haven't actively kept track of
TiLP II development so I don't know if this has already been done or
not.
> 2. src/bsd/link_ser.c contains bad code. Here's the fix (I didn't
> care to use diff):
>
> static int ser_prepare(CableHandle *h)
> {
> // NEW
> int ret;
>
> switch(h->port)
> {
> case PORT_1: h->address = 0x3f8; h->device = strdup("/dev/cuad0"); //NEW
> break;
> case PORT_2: h->address = 0x2f8; h->device = strdup("/dev/cuad1"); //NEW
> break;
> case PORT_3: h->address = 0x3e8; h->device = strdup("/dev/cuad2"); //NEW
> break;
> case PORT_4: h->address = 0x3e8; h->device = strdup("/dev/cuad3"); //NEW
> break;
> default: return ERR_ILLEGAL_ARG;
> }
>
> // detect stuffs
> // OLD: err = check_for_tty(h->device));
> ret = check_for_tty(h->device);
> .
> .
> .
>
> 3. Similarly to (2), all "cuaa"s in src/bsd/link_gry.c have to be
> changed to "cuad"s.
This isn't entirely correct. The name has only been changed since
FreeBSD 6. Everything before that still uses cuaaX.
> As far as run-time goes, USB for the TI-84 Plus at least is borked.
> I'll give just one example:selecting "DirectLink" for the cable type
> and any port for the comm settings gives a dialog box:
>
> =============================================================
> = Msg: failed to open USB device. =
> = Cause: check your USB cable is plugged and/or the =
> = calculator is ON! Check your libusb and usbfs, too. =
> = System: Device not configured (errno = 6) =
> =============================================================
>
> And console output:
> ticables-INFO: found <TI-84 Plus Silver Edition> on #1, version <1.00>
> (tilp-2:6095): ticables-WARNING **: no devices found!
> tilp-INFO: tilp_device_err catched error 37
>
> "libusb" is definitely in there:
> $ ldd tilp-2 | grep usb
> libusb-0.1.so.8 => /usr/local/lib/libusb-0.1.so.8 (0x28bc3000)
I don't have an 84 or 89t, but I'll have a look at it.
|
|
From: Romain <ro...@li...> - 2006-10-04 11:40:03
|
Hi, > As far as run-time goes, USB for the TI-84 Plus at least is borked. I'= ll > give just one example:selecting "DirectLink" for the cable type and any > port for the comm settings gives a dialog box: > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Msg: failed > to open USB device. =3D Cause: check your USB > cable is plugged and/or the =3D calculator is ON! Check your li= busb > and usbfs, too. =3D System: Device not configured (errno =3D 6) > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DAnd > console output: > ticables-INFO: found <TI-84 Plus Silver Edition> on #1, version <1.00= > > (tilp-2:6095): ticables-WARNING **: no devices found! > tilp-INFO: tilp_device_err catched error 37 > > "libusb" is definitely in there: > $ ldd tilp-2 | grep usb > libusb-0.1.so.8 =3D> /usr/local/lib/libusb-0.1.so.8 (0x28bc3000) This is an issue you will have to take a look because I don't have any *BSD system. Maybe, you should attempt to mail Tijl Coosemans which was the original author of the BSD code. > > -- > PGP Key: 0xE354EE3E > keyserver.veridis.com:11371/ roms. > > -----------------------------------------------------------------------= -- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV_______________________________________________ > TiLP-devel mailing list > TiL...@li... > https://lists.sourceforge.net/lists/listinfo/tilp-devel > --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Romain <ro...@li...> - 2006-10-04 11:38:26
|
Hi, > 2. src/bsd/link_ser.c contains bad code. Here's the fix (I didn't care > 3. Similarly to (2), all "cuaa"s in src/bsd/link_gry.c have to be changed > to "cuad"s. Thank you for your 'patch'. roms. --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Romain <ro...@li...> - 2006-10-04 11:35:21
|
Hi, Sean McLaughlin a =E9crit : > Well, I managed to get TiLP-II to compile and run moderately successful= ly > on FreeBSD, but there were some issues: > > 1. src/bsd/detect.c #include's "stdints.h", which doesn't exist. I had= to > pull in the one from the previous version. recently fixed by Kevin for OS-X support. roms. --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Sean M. <sig...@gm...> - 2006-10-04 06:37:58
|
Well, I managed to get TiLP-II to compile and run moderately successfully o=
n FreeBSD, but there were some issues:
1. src/bsd/detect.c #include's "stdints.h", which doesn't exist. I had to =
pull in the one from the previous version.
2. src/bsd/link_ser.c contains bad code. Here's the fix (I didn't care to =
use diff):
static int ser_prepare(CableHandle *h)
{
// NEW
int ret;
switch(h->port)
{
case PORT_1: h->address =3D 0x3f8; h->device =3D strdup("/dev/cuad0"); /=
/NEW
break;
case PORT_2: h->address =3D 0x2f8; h->device =3D strdup("/dev/cuad1"); /=
/NEW
break;
case PORT_3: h->address =3D 0x3e8; h->device =3D strdup("/dev/cuad2"); /=
/NEW
break;
case PORT_4: h->address =3D 0x3e8; h->device =3D strdup("/dev/cuad3"); /=
/NEW
break;
default: return ERR_ILLEGAL_ARG;
}
// detect stuffs
// OLD: err =3D check_for_tty(h->device));
ret =3D check_for_tty(h->device);
.
.
.
3. Similarly to (2), all "cuaa"s in src/bsd/link_gry.c have to be changed t=
o "cuad"s.
As far as run-time goes, USB for the TI-84 Plus at least is borked. I'll g=
ive just one example:selecting "DirectLink" for the cable type and any port=
for the comm settings gives a dialog box:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D Msg: failed to open USB device. =3D
=3D Cause: check your USB cable is plugged and/or the =3D
=3D calculator is ON! Check your libusb and usbfs, too. =3D
=3D System: Device not configured (errno =3D 6) =3D
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
And console output:
ticables-INFO: found <TI-84 Plus Silver Edition> on #1, version <1.00>
(tilp-2:6095): ticables-WARNING **: no devices found!
tilp-INFO: tilp_device_err catched error 37
"libusb" is definitely in there:
$ ldd tilp-2 | grep usb
libusb-0.1.so.8 =3D> /usr/local/lib/libusb-0.1.so.8 (0x28bc3000)
--=20
PGP Key: 0xE354EE3E
keyserver.veridis.com:11371/
|
|
From: Romain <ro...@li...> - 2006-10-03 11:54:47
|
Hi, TiLP2 and TiEmu3 has been successfully ran on 'Windows Vista Ultimate Edition RC1' (32-bits). The LPG's Silver/DirectLink USB driver installs fine on Vista. Enjoy, roms! --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Romain <ro...@li...> - 2006-09-28 05:29:16
|
Hi Benjamin,
> (1) libtifiles2 reports an error when a file has an invalid checksum.
> That's nice, but (a) there are an *awful lot* of files out there that h=
ave
> perfectly good data and incorrect checksums -- TiLP itself has been kno=
wn
> to generate such files on occasion -- and (b) TiLP gives absolutely no
> indication of the error, silently omitting the file and leaving the use=
r
> to wonder what is going on. I guess this was a problem before, but I o=
nly
> just noticed it.
TiLP raises an error when file has an incorrect checksum except when drag=
ged.
I have disabled checksum verification.
> (2) When I double-click on the device name, a lovely dialog box pops up
> saying something along the lines of "Hardware Version: 1 / Boot Version=
:
> 1.0 / Os Version: 1.1 / Battery: good". ("OS" should be capitalized, b=
ut
done
> that's not my main complaint.) The version numbers are truncated, beca=
use
> libticalcs2 does something like
>
> snprintf(infos->os_version, 4, "%1i.%02i", buf[0], buf[1]);
>
> which writes at most three characters plus a zero.
>
> This is actually a sign of a more serious problem. I'm guessing that t=
he
> reason nobody noticed this bug is that it was only tested on Windows. =
As
> it turns out, Microsoft's implementation of snprintf is non-standard (h=
ey,
> it's Microsoft, what do you expect?) -- in fact, if the formatted strin=
g
> is too long, Microsoft's snprintf won't null-terminate the result.
>
> This makes me extremely suspicious of all the other instances of snprin=
tf
> (82 in libticalcs2, 1 in libticables2, 11 in TiLP.)
>
> The simplest way to fix this is to use GLib's g_snprintf instead, which
> conforms to C99 on all platforms (i.e., the result is null-terminated, =
and
> the return value is sensible.)
ok
>
> Benjamin Moody
>
Thanks.
>
> -----------------------------------------------------------------------=
--
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> TiLP-devel mailing list
> TiL...@li...
> https://lists.sourceforge.net/lists/listinfo/tilp-devel
>
--=20
Romain Li=E9vin : <ro...@li...>
Web site : http://www.lievin.net
"Linux, y'a moins bien mais c'est plus cher !"
|
|
From: Benjamin M. <bm...@WP...> - 2006-09-27 01:08:04
|
A couple problems in TiLP II 1.00:
(1) libtifiles2 reports an error when a file has an invalid checksum.
That's nice, but (a) there are an *awful lot* of files out there that have
perfectly good data and incorrect checksums -- TiLP itself has been known
to generate such files on occasion -- and (b) TiLP gives absolutely no
indication of the error, silently omitting the file and leaving the user
to wonder what is going on. I guess this was a problem before, but I only
just noticed it.
(2) When I double-click on the device name, a lovely dialog box pops up
saying something along the lines of "Hardware Version: 1 / Boot Version:
1.0 / Os Version: 1.1 / Battery: good". ("OS" should be capitalized, but
that's not my main complaint.) The version numbers are truncated, because
libticalcs2 does something like
snprintf(infos->os_version, 4, "%1i.%02i", buf[0], buf[1]);
which writes at most three characters plus a zero.
This is actually a sign of a more serious problem. I'm guessing that the
reason nobody noticed this bug is that it was only tested on Windows. As
it turns out, Microsoft's implementation of snprintf is non-standard (hey,
it's Microsoft, what do you expect?) -- in fact, if the formatted string
is too long, Microsoft's snprintf won't null-terminate the result.
This makes me extremely suspicious of all the other instances of snprintf
(82 in libticalcs2, 1 in libticables2, 11 in TiLP.)
The simplest way to fix this is to use GLib's g_snprintf instead, which
conforms to C99 on all platforms (i.e., the result is null-terminated, and
the return value is sensible.)
Benjamin Moody
|
|
From: Romain <ro...@li...> - 2006-09-24 21:47:27
|
Hi, > still a problem: There's still only one TIEXPORT macro, controlled by a= ll fixed. exportX.h -> TIEXPORTX roms. --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Romain <ro...@li...> - 2006-09-24 08:06:22
|
Hi, > I don't see that defined at all in the libticables2 configure.ac. Fix: it's automatically defined by configure checks in MSys term: < checking if gcc supports -fno-rtti -fno-exceptions... yes checking for gcc option to produce PIC... -DDLL_EXPORT checking if gcc PIC flag -DDLL_EXPORT works... yes checking if gcc supports -c -o file.o... yes > > Anyway, we'll need to define the per-lib export there (e.g. > TICABLES_EXPORT > etc.), not DLLEXPORT. I agree and it will be done! > > Kevin Kofler > roms. --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Kevin K. <kev...@ch...> - 2006-09-24 07:58:04
|
> > Also, where are these TI*_EXPORT defined? In the M$VC projects only?
> > These need to be defined from configure.ac too!
>
> They are defined in MSVC (when creating DLL project) and in configure.ac
> for MinGW (DLLEXPORT).
I don't see that defined at all in the libticables2 configure.ac.
Anyway, we'll need to define the per-lib export there (e.g. TICABLES_EXPORT
etc.), not DLLEXPORT.
Kevin Kofler
|
|
From: Romain <ro...@li...> - 2006-09-24 07:54:54
|
Hi, > Well, this (almost certainly) fixes the link failure on OS X, but there= is > still a problem: There's still only one TIEXPORT macro, controlled by a= ll > for > TI*_EXPORT defines. This means that where e.g. libticalcs2 uses a funct= ion > from libticables2, that function is declared as dllexport instead of > dllimport. I wonder how and why this works, because it is clearly wrong= . > There needs to be a different export macro for each library, i.e.: > #ifdef TICABLES_EXPORT > #define TICABLESEXPORT __declspec(dllexport) > #else > #define TICABLESEXPORT __declspec(dllimport) > #endif > and then use TICABLESEXPORT instead of TIEXPORT throughout libticables2 > (yes, > this needs a global replace in each library). ok, I will do it. > Also, where are these TI*_EXPORT defined? In the M$VC projects only? Th= ese > need to be defined from configure.ac too! They are defined in MSVC (when creating DLL project) and in configure.ac for MinGW (DLLEXPORT). roms. --=20 Romain Li=E9vin : <ro...@li...> Web site : http://www.lievin.net "Linux, y'a moins bien mais c'est plus cher !" |
379 messages has been excluded from this view by a project administrator.
