Bug#492812: picprog_1.9.0-1(sparc/unstable): FTBFS, error: sys/io.h: No such file or directory

Thanks. We should find a way to disable that on sparc then. I'm not sure I have time to think about it soon, but I'll try. Jaakko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#417475: FTBFS with GCC 4.3: missing #includes

On Sat, 9 Jun 2007, Jan Wagemakers wrote: picport.cc:181: warning: suggest parentheses around within || etc.. These warnings can probably be solved by placing parentheses, but I'm not sure about where exactly to place them. Anyone suggestions? Well these warnings are kind of useful for

Bug#412778: Debian Bug report logs - #412778 : no support for pic12f635, problem with multi-confword chips

Thanks Jan for the report. I have however very little time to work on picprog in the coming weeks, so implementing this feature request may take time. If anyone comes up with patches I may be able to include it in code faster. Jaakko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a

Bug#387185: picprog: Fails to detect programmer in amd64

Good point, I'll switch that default the other way, and will re-release 1.8.2 today, or 1.8.3. I have no time for this to research this fully, so the working defaults make sense and I'll put --enable-rdtsc for those in need for speed. On Thu, 28 Sep 2006, Steinar H. Gunderson wrote: On

Bug#387185: picprog: Fails to detect programmer in amd64

The default is changed now. --nordtsc is the default --rdtsccan be used for speed Jaakko On Thu, 28 Sep 2006, Steinar H. Gunderson wrote: On Mon, Sep 25, 2006 at 10:49:59PM +0200, Jan Wagemakers wrote: When I try to download this file I get an error: | Forbidden | | You don't have

Bug#387185: picprog: Fails to detect programmer in amd64

Hi, Thanks Jan for collecting feedback on this and debugging things, as well as thanks for all users for interest in getting it to work. I guess any variable clockrates very common in laptops and recent AMD64 cpu's will also not work. I implemented --nordtsc and --slow options, and put

Bug#208692: picprog doesn't compile with g++-4.1

Hi Jan, Thanks for noticing this, I'll fix this in my source. To compile, just remove the picport:: part in front of that set_clock_data definition in picport.h. I think I am not going to release anything for this fix. Maybe if I have time, maybe next winter, I'll create something for

Bug#208692: picprog : pic18f4620 support

It is there now, 1.8.1. Hopefully I did not make mistakes when I put it there. Jaakko -- Foreca Ltd [EMAIL PROTECTED] Pursimiehenkatu 29-31 B, FIN-00150 Helsinki, Finland http://www.foreca.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with

Bug#208692: picprog : pic18f4620 support

Hi Jan, How embarrassing. I do not know if I bother releasing a new version, or just patch 1.8 there. Jaakko On Sat, 25 Mar 2006, Jan Wagemakers wrote: Jaakko, Today, I wanted to write a HEX-file to a pic18f4620 with picprog, but I had no success. Taking a look at hexfile.cc, I noticed