Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030274AbWJCQIl (ORCPT ); Tue, 3 Oct 2006 12:08:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030363AbWJCQIl (ORCPT ); Tue, 3 Oct 2006 12:08:41 -0400 Received: from khc.piap.pl ([195.187.100.11]:43471 "EHLO khc.piap.pl") by vger.kernel.org with ESMTP id S1030274AbWJCQIk (ORCPT ); Tue, 3 Oct 2006 12:08:40 -0400 To: Ben Greear Cc: linux-kernel Subject: Re: Question on HDLC and raw access to T1/E1 serial streams. References: <451DC75E.4070403@candelatech.com> <451EE973.10907@candelatech.com> <45200BD7.6030509@candelatech.com> <45213E53.6090507@candelatech.com> From: Krzysztof Halasa Date: Tue, 03 Oct 2006 18:08:38 +0200 In-Reply-To: <45213E53.6090507@candelatech.com> (Ben Greear's message of "Mon, 02 Oct 2006 09:29:07 -0700") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 773 Lines: 23 Ben Greear writes: > I would definitely want the driver/hardware to deal with the byte/bit > boundaries. But, > the user-space read API could be similar to UDP (or HDLC if I > understand it correctly), I think so. > Before I settle on hardware, I'd like to have some idea that the NIC > can deal with raw > bit-streams. I will look at FALC docs. Most (?) sync serial processors can RX/TX transparent data (though for E3 rates it would be better to have some hardware support). -- Krzysztof Halasa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/