From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 17 00:39:25 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A3946795; Mon, 17 Mar 2014 00:39:25 +0000 (UTC) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5C75C847; Mon, 17 Mar 2014 00:39:25 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id as1so4805373iec.3 for ; Sun, 16 Mar 2014 17:39:24 -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=Pz7o/xAC3GBZiuQxYgzRlvmAsyGfXVCmDlI/nKqQrrg=; b=VSuFS/9Opzz3OuXfMg2YjmhhwLgdYuFchGte1kRncEkyABMzTM2PrE6LWmGASrF2Ig GXWRoH+Ooy4Pj3GDT9EnDQwQfzmnsOpjOn7woRZWfDNfYteykDNdKw9QiONRSPROiHdn oJhwj4wfMxwT9JU1umyEzQnOKTcjZ7BA3IwgWFOIFHP6xyw5IbvOgA0pZhXlSI9CiZfk Ya72FgOX/VNuRbmgEHz2kjid/1VsE80IyzibDiIT7OJ7ZP2/bqqGQOPnB2paxXRuqBZD ZWU7dVbkRYbOJrodIMh+tu4uiwSTL6fQdXP0BEtsrPdH5T4kWTM3UJk9wfmTtDrBJBH5 J19Q== MIME-Version: 1.0 X-Received: by 10.42.214.80 with SMTP id gz16mr16946249icb.6.1395016764851; Sun, 16 Mar 2014 17:39:24 -0700 (PDT) Received: by 10.64.107.3 with HTTP; Sun, 16 Mar 2014 17:39:24 -0700 (PDT) In-Reply-To: References: Date: Mon, 17 Mar 2014 08:39:24 +0800 Message-ID: Subject: Re: [GSoC 2014] Interested in ARM bringup tasks From: Ganbold Tsagaankhuu To: Alexander Tarasikov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-hackers@freebsd.org, "freebsd-arm@freebsd.org" , "Wojciech A. Koszek" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Mar 2014 00:39:25 -0000 Alexander, On Mon, Mar 17, 2014 at 7:19 AM, Alexander Tarasikov < alexander.tarasikov@gmail.com> wrote: > Hello, FreeBSD community! > > I am interested in participating in GSoC this year and I'd like to > pick up one of the tasks related to porting FreeBSD to new > architectures. I'm now doing my master's degree in software > engineering at the "Higher School of Economics" in Moscow. > > Since I love ARM and smartphones, I've chosen the project to port > FreeBSD to a smartphone. If that task is already occupied (which > doesn't seem so), I would be happy to pick up another task suggested > by the community. > > I want to port FreeBSD to the Sony Xperia Z phone. This phone has the > Qualcomm APQ8064 SoC which is used in a large number of smartphones, > including Google Nexus 4. Besides, Qualcomm SoCs are developed > incrementally so there's a high chance that the code for current > generation of chips will benefit future revisions as well. > Interesting. I'm not quite sure how accessible is some pins like uart in Experia Z. I have it here, but I still didn't try to open it yet to see the pins etc. Probably you meant here some embedded boards like ifc6410. Plus ifc6410 has docs so that could be useful too. > > It is known that debugging like JTAG and flash recovery is not > available on consumer devices because of DRM and general love for > obfuscation among the vendors. Therefore, to prevent bricking the > device, That is the hell, it seems Qualcomm uses lauterbach jtag adapter in that case. I and my friend and also some people have tried some adapters like flyswatter2 with ifc6410, still no luck. I suggest using the chainloading approach, that is using the > bootloader that ships with the device and pretend to be a linux image. > That can be done. Their bootloader like maybe LK in case of ifc6410 can boot freebsd kernel. Actually I did that for ifc6410. > > For the mid-term I want to port the u-boot bootloader and add the > support for accessing the microSD card from it. The u-boot will be > flashed to the device instead of the linux kernel. > That could be cool. > > Since the proprietary bootloader already initializes the display (we > can also port linux driver to u-boot), it should be possible, at least > during the initial stage, to use a simple driver in FreeBSD that would > write to the framebuffer allocated by the bootloader or only write the > framebuffer address to the display controller. > That is nice. However first we need uart driver, then either usb ehci, mmc or sata driver needs to mount rootfs in order to boot freebsd to multiuser mode. I already have timer driver and minimal console driver so it makes booting little bit easier. > > In the past I've successfully ported linux to an Intel XScale-based > Asus P525 smartphone, ported Android with all hardware working to boot > from NAND on the Sony Xperia X1 phone and have ported various boards > from OEM to vanilla kernel trees. Recently I've experimented with the > XNU kernel (the one which is used in the fruity operating system) and > ported it to the OMAP5 board. So I think I'll be able to pull it off. > Cool. In case of android or linux there are many people working on various stuffs so in most case drivers are either written or somebody has got started working on particular driver already. For FreeBSD case it is different. You maybe know that very few people are working in case of ARM platform bringup, so we need more developers and I'm happy that you decided to work on this direction. Ganbold > > Have a nice day! > > -- > Regards, Alexander > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >