From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ipaq dual pcmcia sleeve unsupported? (or so it seems)
Date: Thu, 17 Oct 2002 00:47:23 +0200 [thread overview]
Message-ID: <200210162247.g9GMlNG07289@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Thu, 17 Oct 2002 00:19:23 +0200." <200210162219.g9GMJNl07169@zamenhof.cs.utwente.nl>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
Below are the ``raw'' hacks (including all my debugging code).
To give a clearer picture of the changes, and of the actual
resulting code I attached a gzipped tar that contains a diff file ``diffs''
compared to nemo's tar ball, together with those files that I changed for
the dual pcmcia pack.
I'm pretty sure things need still attention, look e.g. for LINKUP_PRC_APOE
Also, the code just looks for the first linkup chip and then assumes
a dual slot pcmcia pack, so the second one should be there as well
(which will not be the case for the expension plus pack).
This could be dealt with using sleeve identification, I suppose.
But then again, this is the code exactely at the point where it
(finally) worked for the first time...
Cheers,
Axel.
[-- Attachment #2: Type: application/octet-stream, Size: 14617 bytes --]
next prev parent reply other threads:[~2002-10-16 22:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 22:01 presotto
2002-10-16 22:19 ` Axel Belinfante
2002-10-16 22:47 ` Axel Belinfante [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-22 15:01 Fco.J.Ballesteros
2002-10-17 15:48 Fco.J.Ballesteros
2002-10-17 16:05 ` Stephen Parker
2002-10-17 14:43 Fco.J.Ballesteros
2002-10-17 14:16 Sape Mullender
2002-10-17 14:42 ` Stephen Parker
2002-10-17 8:29 Fco.J.Ballesteros
2002-10-13 14:11 Sape Mullender
2002-10-16 21:48 ` Axel Belinfante
2002-10-17 13:24 ` Axel Belinfante
2002-10-13 12:46 Axel Belinfante
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=200210162247.g9GMlNG07289@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--cc=9fans@cse.psu.edu \
/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).