From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,7a2d45f282a1da1c X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-08-16 08:29:39 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!newshub.sdsu.edu!elnk-nf2-pas!newsfeed.earthlink.net!stamper.news.pas.earthlink.net!newsread3.news.pas.earthlink.net.POSTED!not-for-mail From: "Matthew Heaney" Newsgroups: comp.lang.ada References: <3F3CCB0F.543478AF@adrianhoe.nospam.com.my> <3f3cd7f4$1_2@news.tm.net.my> <3f3cd84f$1_2@news.tm.net.my> Subject: Re: float with 24-bit resolution X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: Date: Sat, 16 Aug 2003 15:29:39 GMT NNTP-Posting-Host: 65.110.133.134 X-Complaints-To: abuse@earthlink.net X-Trace: newsread3.news.pas.earthlink.net 1061047779 65.110.133.134 (Sat, 16 Aug 2003 08:29:39 PDT) NNTP-Posting-Date: Sat, 16 Aug 2003 08:29:39 PDT Organization: EarthLink Inc. -- http://www.EarthLink.net Xref: archiver1.google.com comp.lang.ada:41586 Date: 2003-08-16T15:29:39+00:00 List-Id: "Jeffrey Creem" wrote in message news:qB6%a.119963$Oz4.25059@rwcrnsc54... > > "Adrian Hoe" wrote in message > news:3f3cd84f$1_2@news.tm.net.my... > > > > 1) Byte Order - The little endian/big endian thing. 24 bit types on little > endian machines talking to big edian H/W (or vice versa).. > 2) Getting the 24 bit type in the first place. How do you get the data from > the HW into memory to work with to start with. It is not > uncommon to have to do 32 bit or 16 bit transfers so you need a method for > getting the data to start with. It doesn't matter: just specify the same T'Small but set T'Size = 32. (In general you should always specify T'Small for fixed point types.) > 3) As another poster mentioned, there is the issue of what you do with the > data once you get it. These fixed point types might be good > as a starting point to get the data into a format that you can begin to work > with but once you start doing calculations on them you will > almost certainly need additional higher resolution fixed point types or > floating point of some precision to do you caculations. Fine: just convert it from the fixed point type to whatever type you desire.