linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: fxload to restictive with address range
Date: Mon, 19 May 2003 00:17:58 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-105330366902576@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105328707423471@msgid-missing>

Kay Sievers wrote:
> 
> I've successfull loaded the firmware into the device with a modified fxload.
> Unfortunately fxload does not support the address range of this chip.
> I changed the following lines and everything is working well.

Better to teach it about that particular chip,
rather than break every standard an21 or fx chip;
just add a new "-t type" option.  "fxload" is
100% correct for the devices it claims to support!

I glanced briefly at that analog.com webpage and
couldn't find any technical specs whatever; so it's
not clear how to handle your particular chip.

Or as a workaround, just use the two stage loader.
If it's EZ-USB compatible, "a3load.hex" should work.

- Dave



> --- ezusb.c     2003-05-18 22:15:20.000000000 +0200
> +++ ezusb.c.orig        2002-04-12 06:08:01.000000000 +0200
> @@ -64,8 +64,8 @@
>      /* with 8KB RAM, 0x0000-0x1b3f can be written
>       * we can't tell if it's a 4KB device here
>       */
> -    if (addr <= 0x7b3f)
> -     return ((addr + len) > 0x7b40);
> +    if (addr <= 0x1b3f)
> +     return ((addr + len) > 0x1b40);
>  
>      /* there may be more RAM; unclear if we can write it.
>       * some bulk buffers may be unused, 0x1b3f-0x1f3f
> @@ -361,7 +361,7 @@
>           return -3;
>       }
>  
> -     if ((len * 2) + 11 > strlen(buf)) {
> +     if ((len * 2) + 11 >= strlen(buf)) {
>           fprintf (stderr, "record too short?\n");
>           return -4;
>       }
> 
> 
> 
> I expect more devices of this kind to appear in the future.
> Maybe somebody can check, how to be prepared for larger internal RAM sizes.
> 
> 
> Have a good day
> 
> Kay Sievers
> 
> 





-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful, 
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2003-05-19  0:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18 19:40 fxload to restictive with address range Kay Sievers
2003-05-18 20:39 ` Kay Sievers
2003-05-19  0:17 ` David Brownell [this message]
2003-05-19  1:16 ` Kay Sievers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-hotplug-105330366902576@msgid-missing \
    --to=david-b@pacbell.net \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).