[Fwd: Re: Waiting 4 feedback]

--=-0oEvu/EPy+a2e4+fkYIN
Content-Type: text/plain
Content-Transfer-Encoding: 7bit



--=-0oEvu/EPy+a2e4+fkYIN
Content-Disposition: inline
Content-Description: Forwarded message - Re: [NOUR] Waiting 4 feedback
Content-Type: message/rfc822

Return-Path: <liubo-qOhvQMgWBuvuBjGU1YDckgC/[email protected]>
Received: from mail8.hotbox.ru ([unix socket]) by mail8.hotbox.ru (Cyrus
	v2.2.3) with LMTP; Tue, 13 Apr 2004 09:27:13 +0400
X-Sieve: CMU Sieve 2.2
Received: from mx2.hotbox.ru (mx2.hotbox.ru [80.68.244.122]) by
	mail8.hotbox.ru (8.12.11/8.12.6) with ESMTP id i3D5RCnS052297 for
	<[email protected]>; Tue, 13 Apr 2004 09:27:13 +0400 (MSD)
	(envelope-from liubo-qOhvQMgWBuvuBjGU1YDckgC/[email protected])
Received: from pc-server.superwaymicro.com ([211.152.157.142]) by
	mx2.hotbox.ru (8.12.11/8.12.11) with ESMTP id i3D5R8Zw021831 for
	<[email protected]>; Tue, 13 Apr 2004 09:27:11 +0400 (MSD) (envelope-from
	liubo-qOhvQMgWBuvuBjGU1YDckgC/[email protected])
Received: from shanghai (unknown [172.24.195.115]) by
	pc-server.superwaymicro.com (Postfix) with SMTP id F065876A20 for
	<[email protected]>; Tue, 13 Apr 2004 13:19:09 +0800 (CST)
Message-ID: <000701c42118$0d09bc10$73c318ac-qOhvQMgWBuvuBjGU1YDckgC/[email protected]>
From: =?utf-8?B?5YiY5Y2a?= <liubo-qOhvQMgWBuvuBjGU1YDckgC/[email protected]>
To: <[email protected]>
References: <200403221438.i2MEctWF079899-4369N2AgR01DZVVK0I9FoQ@public.gmane.org>
Subject: Re: [NOUR] Waiting 4 feedback
Date: Tue, 13 Apr 2004 13:27:44 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-SpamTest-Status: Probable Spam
X-SpamTest-Info: Profile: Archiving/Rejecting (2/030321)
X-SpamTest-Info: Profile: Detect Hard (4/030526)
X-SpamTest-Info: Profile: Formal (72/040412)
X-SpamTest-Info: {relay has no DNS name}
X-SpamTest-Method: DNS: not in DNS
Content-Transfer-Encoding: 7bit

Hi, Mohamed;
        I think you had better briefly describe the frame format  in the beginning of the  document to give designers a top level image of how the bluetooth frame is built.
    In  modules definitions, the bit width of input/output signals isn't specified. So I don't know your input is 1 bit width or 8 bits width.
    Do you think of treating the bitstream of bluetooth byte by bye instead of bit by bit.Blue tooth chip is used in consumer devices which is power sensitive. If you got your working frenquency lower, you can save power dramatically.


cac
      
----- Original Message ----- 
From: "msalem" <[email protected]>
To: <[email protected]>
Sent: Monday, March 22, 2004 10:38 PM
Subject: [NOUR] Waiting 4 feedback


> Dear All,
> 
> Still waiting for your feedback to proceed the
> definition of the
> bitstream Hardware spec.
> Thanks for your time and interest.
> Best Regards,
> 
> Mohamed A.Salem
> 
> --------------------------
> NOUR Mailing List
> Handasa Arabia Organization
> http://www.handasarabia.org
> [email protected]
> 
> Message number 133

--=-0oEvu/EPy+a2e4+fkYIN
Content-Type: text/plain; charset=us-ascii

--------------------------
NOUR Mailing List
Handasa Arabia Organization
http://www.handasarabia.org
[email protected]

Message number 134
--=-0oEvu/EPy+a2e4+fkYIN--