From owner-freebsd-arm@FreeBSD.ORG Tue Jul 2 18:20:17 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1EF7E834; Tue, 2 Jul 2013 18:20:17 +0000 (UTC) (envelope-from jkwilborn@gmail.com) Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) by mx1.freebsd.org (Postfix) with ESMTP id E738A1E1A; Tue, 2 Jul 2013 18:20:16 +0000 (UTC) Received: by mail-pa0-f50.google.com with SMTP id fb1so6617124pad.9 for ; Tue, 02 Jul 2013 11:20:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=I0VFtTJUMWqpgs8ozlGGkL53SsP2EcVSjEgXhyKOGj0=; b=gY2A/eYFyp627TQxZhv9+r/yljGaGUk+geRfJW+w/30HLdTFOVQ2bUH8aUqQadl2YG wp4wB/2KtnpXnRWHQYLw+/kesvqiZh3+v8VcTc0ouqrCuqGdli9tfktMrVbsXdNdhjV1 swzIeCFwMqLYCbNXlWfY9Ad2ksteR5rf0CoIVHyg5CdFTWtp/F8YmtFmpYQoi8r3Fm24 PeEl+P+E+jiaCktvOMfAE7iqCpC73ohdt0uXQj8cjOQaWQa/uwwlAhQTejzVovkBAjA2 HUMoRcpkOothrI9NLCpa3kuuInIyfyDnx419yNAPrgAlbLWX3uEFQoANjdwFy9TNTv3a QEhw== MIME-Version: 1.0 X-Received: by 10.68.50.69 with SMTP id a5mr30575816pbo.122.1372789216736; Tue, 02 Jul 2013 11:20:16 -0700 (PDT) Received: by 10.66.26.241 with HTTP; Tue, 2 Jul 2013 11:20:16 -0700 (PDT) In-Reply-To: <51D3097A.8010601@FreeBSD.org> References: <20130702145905.GA1847@olymp.kibab.com> <51D3097A.8010601@FreeBSD.org> Date: Tue, 2 Jul 2013 11:20:16 -0700 Message-ID: Subject: Re: [PATCH] SDIO support for Globalscale Dreamplug From: Jack Wilborn To: Alexander Motin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-arm@freebsd.org, Ilya Bakulin , freebsd-embedded@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jul 2013 18:20:17 -0000 Nice, how do we include this code in our builds? How is it invoked? Main question is that are these structures in an area that is protected so that only root can modify them? I don't know enough about about SD cards to know if they are alike in the communications to them. I'd like to see more about this and see it in the test bed to give you more feedback. Having taught C for 15 years, I'm ok with reading and understanding the code, but to make it usable is the bottom line. Nice work, I'm sure it would be an asset to all of us. I'm a little groggy about this so if I missed anything, please overlook it. I like it! Jack On Tue, Jul 2, 2013 at 10:10 AM, Alexander Motin wrote: > On 02.07.2013 17:59, Ilya Bakulin wrote: > >> Hi list, >> I'm currently developing a SDIO driver for the Globalscale Dreamplug. >> I have taken SDIO patch for Marvell SoC from [1]. >> After that I have written some SDIO-related code in sys/dev/mmc/mmc.c, >> using OpenBSD SDIO code and the patch from Ben Gray ([2]) as a starting >> point. >> >> I have taken Warner's wish to have SDIO code in MMC bus into account, so >> there >> is no extra layer of abstraction in my code, SDIO devices will attach >> directly >> to MMC bus. This makes possible to implement combo cards support in the >> future, >> although I don't support them in my code atm. >> >> What is already implemented: >> * SDIO card detection; >> * CIS reading, both common CIS and individual functions' CIS; >> * Function enable. >> >> My questions, need answers before I can move further: >> * Where should I store information retrieved from the CIS? >> As far as I understand, I should use mmc_ivars structure for that. >> But in SDIO case the relationship between MMC bus and SDIO card is >> 1:1, >> and storing the information about the card in mmc_softc sounds like >> a good idea -- then I can pass only mmc_softc structure to all >> functions >> that need to work with the attached SDIO card. >> > > I think SD world is a terrible mess by itself. I would like to not add > more. Functions that suppose card access should take card-specific > structure or device as an argument, not a bus ones. > > > * Should I add any methods to the existing interface files? >> >> * Are there any devices on the market that use SDIO interface and which >> chipsets are supported in FreeBSD? Any Atheros devices? >> Adrian, what do you think? >> I have only Dreamplug with Marvell SDIO-based WLAN chip, that doesn't >> have >> an opensource driver even for Linux... >> > > Recently I've bought EyeFi card hoping it is combined SD+SDIO, but seems > like card's WiFi part is completely autonomous and controlled via file > access on storage and not really SDIO. > > I would try to look for SDIO Bluetooth card. I think such ones still could > be found on eBay, and I think there are some specifications for that. > Though I've never looked inside. > > > [1] http://people.freebsd.org/~**raj/misc/mv_sdio.c >> [2] http://lists.freebsd.org/**pipermail/freebsd-arm/2012-** >> June/003543.html >> > > -- > Alexander Motin > > ______________________________**_________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@**freebsd.org > " >