From owner-freebsd-arm@FreeBSD.ORG Mon Jul 19 11:06:53 2010 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48A991065678 for ; Mon, 19 Jul 2010 11:06:53 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 36E938FC27 for ; Mon, 19 Jul 2010 11:06:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6JB6rW7065647 for ; Mon, 19 Jul 2010 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6JB6qb2065645 for freebsd-arm@FreeBSD.org; Mon, 19 Jul 2010 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 19 Jul 2010 11:06:52 GMT Message-Id: <201007191106.o6JB6qb2065645@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-arm@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2010 11:06:53 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o arm/148474 arm MMC timeout too short durring enumeration of cards. o arm/134368 arm [patch] nslu2_led driver for the LEDs on the NSLU2 o arm/134338 arm [patch] Lock GPIO accesses on ixp425 3 problems total. From owner-freebsd-arm@FreeBSD.ORG Mon Jul 19 13:39:40 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 684C0106566C for ; Mon, 19 Jul 2010 13:39:40 +0000 (UTC) (envelope-from gja@ansley.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2C19A8FC13 for ; Mon, 19 Jul 2010 13:39:39 +0000 (UTC) Received: by gwb19 with SMTP id 19so1966134gwb.13 for ; Mon, 19 Jul 2010 06:39:39 -0700 (PDT) Received: by 10.151.63.18 with SMTP id q18mr4757112ybk.100.1279544977577; Mon, 19 Jul 2010 06:09:37 -0700 (PDT) Received: from G5.internal.ansley.com (99-135-104-139.lightspeed.tukrga.sbcglobal.net [99.135.104.139]) by mx.google.com with ESMTPS id q21sm3794913ybk.3.2010.07.19.06.09.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 19 Jul 2010 06:09:36 -0700 (PDT) Sender: Greg Ansley Message-ID: <4C444E8B.6090104@ansley.com> Date: Mon, 19 Jul 2010 09:09:31 -0400 From: Greg Ansley User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: at91sam9g20: Upcoming Patches X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2010 13:39:40 -0000 During the next day or so I'll be submitting the following patches for the arm/at91 (head) tree with the goal of eventually being able to create a single "GENERIC" kernel that will boot on the at91rm9200, at91sam926? and at91sam9g20 (as long as boot sequence configures the multiplexed pins). I also have patches against 8-current if any one needs them. These patches have been tested on a KB9202C and an Atmel AT91SAM9G20EK Rev B. I would appreciate testing (or loan of boards) for the at91sam926? family. I am assuming it would be best to submit separate PRs for each of the changes. If something else is preferred let me know. at91_mci.c: * Compile and run time selection of "Slot B" of mci controller. * Compile and run time selection of 4 wire connection (4x bandwidth to slot). * No byte swapping on non-RM9200 targets. * Fix obscure segfault when bus_dma_load() fails in at91_mci_start_cmd(). at91_pit.c: * Support for full resolution timer counter. * Remove compile time address dependencies. at91_rst.c: (NEW) * Support SAM9 reset controller. * Implement shutdown() on NRST (reset button) and full reset if held for more the 5 seconds. at91_wdt.c: (NEW) * Support SAM9 watchdog timer using the watchdog(9) style interface. if_ate.c: * Support for sam9 "EMAC" controller. * Support for rmii interface to phy. at91.c & at91sam9.c: * Eliminate separate at91sam9.c file. * Add new devices to at91sam9_devs table. at91_machdep.c & at at91sam9_machdep.c: * Automatic chip type determination. * Remove compile time chip dependencies. * Eliminate separate at91sam9_machdep.c file. at91_pmc.c: * Corrected support for all of the sam926? and sam9g20 chips. * Remove compile time chip dependencies. Greg Ansley From owner-freebsd-arm@FreeBSD.ORG Mon Jul 19 14:19:41 2010 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E24BF106564A for ; Mon, 19 Jul 2010 14:19:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 754F18FC0C for ; Mon, 19 Jul 2010 14:19:41 +0000 (UTC) Received: from [10.0.0.3] (warner-iphone.bsdimp.com [10.0.0.3]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o6JEGj6s037342; Mon, 19 Jul 2010 08:16:46 -0600 (MDT) (envelope-from imp@bsdimp.com) From: Warner Losh To: Greg Ansley In-Reply-To: <4C444E8B.6090104@ansley.com> X-Mailer: iPhone Mail (7D11) References: <4C444E8B.6090104@ansley.com> Message-Id: <62D59897-79BD-4AF2-8584-F045970712F5@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (iPhone Mail 7D11) Date: Mon, 19 Jul 2010 08:16:34 -0600 Cc: "freebsd-arm@FreeBSD.org" Subject: Re: at91sam9g20: Upcoming Patches X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2010 14:19:42 -0000 I'd prefer one big patch, assuming it is almost ready to roll into the tree. Chances ate I'll be committing it. Bit there might also be a second effort that has patches in flight too. There was some talk too of investgating fdt to cope with the different families. Btw, when I was doing the original port I found the multiplexed pins were rarely configured by the wide array of boot loaders... You were lucky if the memory and nic pins were configured. Warner On Jul 19, 2010, at 7:09 AM, Greg Ansley wrote: > During the next day or so I'll be submitting the following patches > for the arm/at91 (head) tree with the goal of eventually being able > to create a single "GENERIC" kernel that will boot on the > at91rm9200, at91sam926? and at91sam9g20 (as long as boot sequence > configures the multiplexed pins). > > I also have patches against 8-current if any one needs them. > > These patches have been tested on a KB9202C and an Atmel > AT91SAM9G20EK Rev B. I would appreciate testing (or loan of boards) > for the at91sam926? family. > > I am assuming it would be best to submit separate PRs for each of > the changes. If something else is preferred let me know. > > at91_mci.c: > > * Compile and run time selection of "Slot B" of mci controller. > * Compile and run time selection of 4 wire connection (4x bandwidth > to slot). > * No byte swapping on non-RM9200 targets. > * Fix obscure segfault when bus_dma_load() fails in > at91_mci_start_cmd(). > > at91_pit.c: > > * Support for full resolution timer counter. > * Remove compile time address dependencies. > > at91_rst.c: (NEW) > > * Support SAM9 reset controller. > * Implement shutdown() on NRST (reset button) and full reset if held > for more the 5 seconds. > > at91_wdt.c: (NEW) > > * Support SAM9 watchdog timer using the watchdog(9) style interface. > > if_ate.c: > > * Support for sam9 "EMAC" controller. > * Support for rmii interface to phy. > > at91.c & at91sam9.c: > > * Eliminate separate at91sam9.c file. > * Add new devices to at91sam9_devs table. > > at91_machdep.c & at at91sam9_machdep.c: > > * Automatic chip type determination. > * Remove compile time chip dependencies. > * Eliminate separate at91sam9_machdep.c file. > > at91_pmc.c: > > * Corrected support for all of the sam926? and sam9g20 chips. > * Remove compile time chip dependencies. > > Greg Ansley > > _______________________________________________ > 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" > > From owner-freebsd-arm@FreeBSD.ORG Mon Jul 19 14:41:07 2010 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16F56106564A for ; Mon, 19 Jul 2010 14:41:07 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id 7496C8FC15 for ; Mon, 19 Jul 2010 14:41:06 +0000 (UTC) Received: from localhost (unknown [213.17.239.109]) by smtp.semihalf.com (Postfix) with ESMTP id AD503C42DF; Mon, 19 Jul 2010 16:41:04 +0200 (CEST) X-Virus-Scanned: by amavisd-new at semihalf.com Received: from smtp.semihalf.com ([213.17.239.109]) by localhost (smtp.semihalf.com [213.17.239.109]) (amavisd-new, port 10024) with ESMTP id ovZYc4rGwJye; Mon, 19 Jul 2010 16:41:03 +0200 (CEST) Received: from [10.0.0.79] (cardhu.semihalf.com [213.17.239.108]) by smtp.semihalf.com (Postfix) with ESMTPSA id DC5F8C42D5; Mon, 19 Jul 2010 16:41:03 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Rafal Jaworowski In-Reply-To: <62D59897-79BD-4AF2-8584-F045970712F5@bsdimp.com> Date: Mon, 19 Jul 2010 16:41:03 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4C444E8B.6090104@ansley.com> <62D59897-79BD-4AF2-8584-F045970712F5@bsdimp.com> To: Warner Losh X-Mailer: Apple Mail (2.1081) Cc: "freebsd-arm@FreeBSD.org" Subject: Re: at91sam9g20: Upcoming Patches X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2010 14:41:07 -0000 On 2010-07-19, at 16:16, Warner Losh wrote: > I'd prefer one big patch, assuming it is almost ready to roll into the = tree. Chances ate I'll be committing it. Bit there might also be a = second effort that has patches in flight too. There was some talk too = of investgating fdt to cope with the different families. Yes, it would be ideal to get AT91 port converted to FDT approach, and = then only deal with a number of DTS files for various boards, but this = would mean more work (as would involve refactoring the AT91 low-level = code for all currently supported variations of the chip). Rafal > Btw, when I was doing the original port I found the multiplexed pins = were rarely configured by the wide array of boot loaders... You were = lucky if the memory and nic pins were configured. >=20 > Warner >=20 >=20 > On Jul 19, 2010, at 7:09 AM, Greg Ansley wrote: >=20 >> During the next day or so I'll be submitting the following patches = for the arm/at91 (head) tree with the goal of eventually being able to = create a single "GENERIC" kernel that will boot on the at91rm9200, = at91sam926? and at91sam9g20 (as long as boot sequence configures the = multiplexed pins). >>=20 >> I also have patches against 8-current if any one needs them. >>=20 >> These patches have been tested on a KB9202C and an Atmel = AT91SAM9G20EK Rev B. I would appreciate testing (or loan of boards) for = the at91sam926? family. >>=20 >> I am assuming it would be best to submit separate PRs for each of the = changes. If something else is preferred let me know. >>=20 >> at91_mci.c: >>=20 >> * Compile and run time selection of "Slot B" of mci controller. >> * Compile and run time selection of 4 wire connection (4x bandwidth >> to slot). >> * No byte swapping on non-RM9200 targets. >> * Fix obscure segfault when bus_dma_load() fails in >> at91_mci_start_cmd(). >>=20 >> at91_pit.c: >>=20 >> * Support for full resolution timer counter. >> * Remove compile time address dependencies. >>=20 >> at91_rst.c: (NEW) >>=20 >> * Support SAM9 reset controller. >> * Implement shutdown() on NRST (reset button) and full reset if held >> for more the 5 seconds. >>=20 >> at91_wdt.c: (NEW) >>=20 >> * Support SAM9 watchdog timer using the watchdog(9) style interface. >>=20 >> if_ate.c: >>=20 >> * Support for sam9 "EMAC" controller. >> * Support for rmii interface to phy. >>=20 >> at91.c & at91sam9.c: >>=20 >> * Eliminate separate at91sam9.c file. >> * Add new devices to at91sam9_devs table. >>=20 >> at91_machdep.c & at at91sam9_machdep.c: >>=20 >> * Automatic chip type determination. >> * Remove compile time chip dependencies. >> * Eliminate separate at91sam9_machdep.c file. >>=20 >> at91_pmc.c: >>=20 >> * Corrected support for all of the sam926? and sam9g20 chips. >> * Remove compile time chip dependencies. >>=20 >> Greg Ansley >>=20 >> _______________________________________________ >> 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" >>=20 >>=20 > _______________________________________________ > 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" From owner-freebsd-arm@FreeBSD.ORG Mon Jul 19 14:44:31 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CFFC106566C for ; Mon, 19 Jul 2010 14:44:31 +0000 (UTC) (envelope-from gja@ansley.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1D2BD8FC17 for ; Mon, 19 Jul 2010 14:44:30 +0000 (UTC) Received: by gyd8 with SMTP id 8so2692316gyd.13 for ; Mon, 19 Jul 2010 07:44:30 -0700 (PDT) Received: by 10.151.25.6 with SMTP id c6mr4018792ybj.228.1279550668977; Mon, 19 Jul 2010 07:44:28 -0700 (PDT) Received: from G5.internal.ansley.com (99-135-104-139.lightspeed.tukrga.sbcglobal.net [99.135.104.139]) by mx.google.com with ESMTPS id q36sm3877760yba.0.2010.07.19.07.44.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 19 Jul 2010 07:44:27 -0700 (PDT) Sender: Greg Ansley Message-ID: <4C4464C9.6080402@ansley.com> Date: Mon, 19 Jul 2010 10:44:25 -0400 From: Greg Ansley User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: Rafal Jaworowski References: <4C444E8B.6090104@ansley.com> <62D59897-79BD-4AF2-8584-F045970712F5@bsdimp.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@FreeBSD.org" Subject: Re: at91sam9g20: Upcoming Patches X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2010 14:44:31 -0000 FDT is on my to do list. But I did not want to hold this up for that. I've already had to rework some thing as the head of the tree and I got out of sync. Greg On 7/19/10 10:41 AM, Rafal Jaworowski wrote: > On 2010-07-19, at 16:16, Warner Losh wrote: > > >> I'd prefer one big patch, assuming it is almost ready to roll into the tree. Chances ate I'll be committing it. Bit there might also be a second effort that has patches in flight too. There was some talk too of investgating fdt to cope with the different families. >> > Yes, it would be ideal to get AT91 port converted to FDT approach, and then only deal with a number of DTS files for various boards, but this would mean more work (as would involve refactoring the AT91 low-level code for all currently supported variations of the chip). > > Rafal > > > >> Btw, when I was doing the original port I found the multiplexed pins were rarely configured by the wide array of boot loaders... You were lucky if the memory and nic pins were configured. >> >> Warner >> >> >> On Jul 19, 2010, at 7:09 AM, Greg Ansley wrote: >> >> >>> During the next day or so I'll be submitting the following patches for the arm/at91 (head) tree with the goal of eventually being able to create a single "GENERIC" kernel that will boot on the at91rm9200, at91sam926? and at91sam9g20 (as long as boot sequence configures the multiplexed pins). >>> >>> I also have patches against 8-current if any one needs them. >>> >>> These patches have been tested on a KB9202C and an Atmel AT91SAM9G20EK Rev B. I would appreciate testing (or loan of boards) for the at91sam926? family. >>> >>> I am assuming it would be best to submit separate PRs for each of the changes. If something else is preferred let me know. >>> >>> at91_mci.c: >>> >>> * Compile and run time selection of "Slot B" of mci controller. >>> * Compile and run time selection of 4 wire connection (4x bandwidth >>> to slot). >>> * No byte swapping on non-RM9200 targets. >>> * Fix obscure segfault when bus_dma_load() fails in >>> at91_mci_start_cmd(). >>> >>> at91_pit.c: >>> >>> * Support for full resolution timer counter. >>> * Remove compile time address dependencies. >>> >>> at91_rst.c: (NEW) >>> >>> * Support SAM9 reset controller. >>> * Implement shutdown() on NRST (reset button) and full reset if held >>> for more the 5 seconds. >>> >>> at91_wdt.c: (NEW) >>> >>> * Support SAM9 watchdog timer using the watchdog(9) style interface. >>> >>> if_ate.c: >>> >>> * Support for sam9 "EMAC" controller. >>> * Support for rmii interface to phy. >>> >>> at91.c& at91sam9.c: >>> >>> * Eliminate separate at91sam9.c file. >>> * Add new devices to at91sam9_devs table. >>> >>> at91_machdep.c& at at91sam9_machdep.c: >>> >>> * Automatic chip type determination. >>> * Remove compile time chip dependencies. >>> * Eliminate separate at91sam9_machdep.c file. >>> >>> at91_pmc.c: >>> >>> * Corrected support for all of the sam926? and sam9g20 chips. >>> * Remove compile time chip dependencies. >>> >>> Greg Ansley >>> >>> _______________________________________________ >>> 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" >>> >>> >>> >> _______________________________________________ >> 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" >> > From owner-freebsd-arm@FreeBSD.ORG Mon Jul 19 14:45:56 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32E80106564A for ; Mon, 19 Jul 2010 14:45:56 +0000 (UTC) (envelope-from gja@ansley.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id E8E248FC15 for ; Mon, 19 Jul 2010 14:45:55 +0000 (UTC) Received: by gyd8 with SMTP id 8so2693298gyd.13 for ; Mon, 19 Jul 2010 07:45:55 -0700 (PDT) Received: by 10.151.63.30 with SMTP id q30mr4510577ybk.154.1279550755149; Mon, 19 Jul 2010 07:45:55 -0700 (PDT) Received: from G5.internal.ansley.com (99-135-104-139.lightspeed.tukrga.sbcglobal.net [99.135.104.139]) by mx.google.com with ESMTPS id q1sm5593469ybk.20.2010.07.19.07.45.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 19 Jul 2010 07:45:54 -0700 (PDT) Sender: Greg Ansley Message-ID: <4C446520.3070900@ansley.com> Date: Mon, 19 Jul 2010 10:45:52 -0400 From: Greg Ansley User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: Warner Losh References: <4C444E8B.6090104@ansley.com> <62D59897-79BD-4AF2-8584-F045970712F5@bsdimp.com> In-Reply-To: <62D59897-79BD-4AF2-8584-F045970712F5@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@FreeBSD.org" Subject: Re: at91sam9g20: Upcoming Patches X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2010 14:45:56 -0000 One big patch it is, it is easier for me as well. I will send it after creating the patch against today's head and testing it on both boards (late today, probably). I found that I can use a generic U-boot and configure the pins in the "bootcmd" and then the kernel can ignore the board specific issues. Obviously the board_xxx.c files are the way to go for a production build but I would really like to make it easy for people to try out FreeBSD on lots of boards without a lot of effort. I intended to write a up a quick wiki with some examples and links to binaries to help get people started... Greg On 7/19/10 10:16 AM, Warner Losh wrote: > I'd prefer one big patch, assuming it is almost ready to roll into the > tree. Chances ate I'll be committing it. Bit there might also be a > second effort that has patches in flight too. There was some talk too > of investgating fdt to cope with the different families. > > Btw, when I was doing the original port I found the multiplexed pins > were rarely configured by the wide array of boot loaders... You were > lucky if the memory and nic pins were configured. > > Warner > > > On Jul 19, 2010, at 7:09 AM, Greg Ansley wrote: > >> During the next day or so I'll be submitting the following patches >> for the arm/at91 (head) tree with the goal of eventually being able >> to create a single "GENERIC" kernel that will boot on the at91rm9200, >> at91sam926? and at91sam9g20 (as long as boot sequence configures the >> multiplexed pins). >> >> I also have patches against 8-current if any one needs them. >> >> These patches have been tested on a KB9202C and an Atmel >> AT91SAM9G20EK Rev B. I would appreciate testing (or loan of boards) >> for the at91sam926? family. >> >> I am assuming it would be best to submit separate PRs for each of the >> changes. If something else is preferred let me know. >> >> at91_mci.c: >> >> * Compile and run time selection of "Slot B" of mci controller. >> * Compile and run time selection of 4 wire connection (4x bandwidth >> to slot). >> * No byte swapping on non-RM9200 targets. >> * Fix obscure segfault when bus_dma_load() fails in >> at91_mci_start_cmd(). >> >> at91_pit.c: >> >> * Support for full resolution timer counter. >> * Remove compile time address dependencies. >> >> at91_rst.c: (NEW) >> >> * Support SAM9 reset controller. >> * Implement shutdown() on NRST (reset button) and full reset if held >> for more the 5 seconds. >> >> at91_wdt.c: (NEW) >> >> * Support SAM9 watchdog timer using the watchdog(9) style interface. >> >> if_ate.c: >> >> * Support for sam9 "EMAC" controller. >> * Support for rmii interface to phy. >> >> at91.c & at91sam9.c: >> >> * Eliminate separate at91sam9.c file. >> * Add new devices to at91sam9_devs table. >> >> at91_machdep.c & at at91sam9_machdep.c: >> >> * Automatic chip type determination. >> * Remove compile time chip dependencies. >> * Eliminate separate at91sam9_machdep.c file. >> >> at91_pmc.c: >> >> * Corrected support for all of the sam926? and sam9g20 chips. >> * Remove compile time chip dependencies. >> >> Greg Ansley >> >> _______________________________________________ >> 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" >> >> From owner-freebsd-arm@FreeBSD.ORG Mon Jul 19 15:36:25 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AAAE106566B for ; Mon, 19 Jul 2010 15:36:25 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id B72D98FC19 for ; Mon, 19 Jul 2010 15:36:24 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o6JFaJIL047103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 19 Jul 2010 17:36:21 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.3/8.14.3) with ESMTP id o6JFaFA1084264 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Jul 2010 17:36:15 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o6JFaFjK031187; Mon, 19 Jul 2010 17:36:15 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o6JFaELn031186; Mon, 19 Jul 2010 17:36:14 +0200 (CEST) (envelope-from ticso) Date: Mon, 19 Jul 2010 17:36:14 +0200 From: Bernd Walter To: Greg Ansley Message-ID: <20100719153614.GI28908@cicely7.cicely.de> References: <4C444E8B.6090104@ansley.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C444E8B.6090104@ansley.com> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: freebsd-arm@freebsd.org Subject: Re: at91sam9g20: Upcoming Patches X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2010 15:36:25 -0000 On Mon, Jul 19, 2010 at 09:09:31AM -0400, Greg Ansley wrote: > During the next day or so I'll be submitting the following patches for > the arm/at91 (head) tree with the goal of eventually being able to > create a single "GENERIC" kernel that will boot on the at91rm9200, > at91sam926? and at91sam9g20 (as long as boot sequence configures the > multiplexed pins). > > I also have patches against 8-current if any one needs them. > > These patches have been tested on a KB9202C and an Atmel AT91SAM9G20EK > Rev B. I would appreciate testing (or loan of boards) for the > at91sam926? family. > > I am assuming it would be best to submit separate PRs for each of the > changes. If something else is preferred let me know. > > at91_mci.c: > > * Compile and run time selection of "Slot B" of mci controller. > * Compile and run time selection of 4 wire connection (4x bandwidth > to slot). > * No byte swapping on non-RM9200 targets. > * Fix obscure segfault when bus_dma_load() fails in > at91_mci_start_cmd(). > > at91_pit.c: > > * Support for full resolution timer counter. > * Remove compile time address dependencies. > > at91_rst.c: (NEW) > > * Support SAM9 reset controller. > * Implement shutdown() on NRST (reset button) and full reset if held > for more the 5 seconds. > > at91_wdt.c: (NEW) > > * Support SAM9 watchdog timer using the watchdog(9) style interface. > > if_ate.c: > > * Support for sam9 "EMAC" controller. > * Support for rmii interface to phy. RM9200 ate requires specific DMA alignment, which required a few realign copys. This isn't neccessary for most other AT91 devices and for sure not with any AT91SAM9x device. Not sure if all of them are automatically avoided - you might want to verify the code about this point. There is also RBNA workaround, which should be RM9200 specifc, which shouldn't be triggered with others, but you might want to save a few bytes codespace. > at91.c & at91sam9.c: > > * Eliminate separate at91sam9.c file. > * Add new devices to at91sam9_devs table. > > at91_machdep.c & at at91sam9_machdep.c: > > * Automatic chip type determination. > * Remove compile time chip dependencies. > * Eliminate separate at91sam9_machdep.c file. > > at91_pmc.c: > > * Corrected support for all of the sam926? and sam9g20 chips. > * Remove compile time chip dependencies. > > Greg Ansley > > _______________________________________________ > 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" -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Mon Jul 19 15:58:13 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91D91106566B for ; Mon, 19 Jul 2010 15:58:13 +0000 (UTC) (envelope-from gja@ansley.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 548048FC13 for ; Mon, 19 Jul 2010 15:58:13 +0000 (UTC) Received: by gwb19 with SMTP id 19so2058026gwb.13 for ; Mon, 19 Jul 2010 08:58:12 -0700 (PDT) Received: by 10.151.116.1 with SMTP id t1mr4783083ybm.329.1279555092373; Mon, 19 Jul 2010 08:58:12 -0700 (PDT) Received: from G5.internal.ansley.com (99-135-104-139.lightspeed.tukrga.sbcglobal.net [99.135.104.139]) by mx.google.com with ESMTPS id x3sm3931617ybl.22.2010.07.19.08.58.10 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 19 Jul 2010 08:58:11 -0700 (PDT) Sender: Greg Ansley Message-ID: <4C447611.1020008@ansley.com> Date: Mon, 19 Jul 2010 11:58:09 -0400 From: Greg Ansley User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: ticso@cicely.de References: <4C444E8B.6090104@ansley.com> <20100719153614.GI28908@cicely7.cicely.de> In-Reply-To: <20100719153614.GI28908@cicely7.cicely.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org, Bernd Walter Subject: Re: at91sam9g20: Upcoming Patches X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2010 15:58:13 -0000 Thanks, I had missed the RBNA issue. I will take a look at the alignment copies (don't recall as I made the changes over a year ago). Greg On 7/19/10 11:36 AM, Bernd Walter wrote: > On Mon, Jul 19, 2010 at 09:09:31AM -0400, Greg Ansley wrote: > >> During the next day or so I'll be submitting the following patches for >> the arm/at91 (head) tree with the goal of eventually being able to >> create a single "GENERIC" kernel that will boot on the at91rm9200, >> at91sam926? and at91sam9g20 (as long as boot sequence configures the >> multiplexed pins). >> >> I also have patches against 8-current if any one needs them. >> >> These patches have been tested on a KB9202C and an Atmel AT91SAM9G20EK >> Rev B. I would appreciate testing (or loan of boards) for the >> at91sam926? family. >> >> I am assuming it would be best to submit separate PRs for each of the >> changes. If something else is preferred let me know. >> >> at91_mci.c: >> >> * Compile and run time selection of "Slot B" of mci controller. >> * Compile and run time selection of 4 wire connection (4x bandwidth >> to slot). >> * No byte swapping on non-RM9200 targets. >> * Fix obscure segfault when bus_dma_load() fails in >> at91_mci_start_cmd(). >> >> at91_pit.c: >> >> * Support for full resolution timer counter. >> * Remove compile time address dependencies. >> >> at91_rst.c: (NEW) >> >> * Support SAM9 reset controller. >> * Implement shutdown() on NRST (reset button) and full reset if held >> for more the 5 seconds. >> >> at91_wdt.c: (NEW) >> >> * Support SAM9 watchdog timer using the watchdog(9) style interface. >> >> if_ate.c: >> >> * Support for sam9 "EMAC" controller. >> * Support for rmii interface to phy. >> > RM9200 ate requires specific DMA alignment, which required a few > realign copys. > This isn't neccessary for most other AT91 devices and for sure > not with any AT91SAM9x device. > Not sure if all of them are automatically avoided - you might want > to verify the code about this point. > There is also RBNA workaround, which should be RM9200 specifc, > which shouldn't be triggered with others, but you might want to save > a few bytes codespace. > > >> at91.c& at91sam9.c: >> >> * Eliminate separate at91sam9.c file. >> * Add new devices to at91sam9_devs table. >> >> at91_machdep.c& at at91sam9_machdep.c: >> >> * Automatic chip type determination. >> * Remove compile time chip dependencies. >> * Eliminate separate at91sam9_machdep.c file. >> >> at91_pmc.c: >> >> * Corrected support for all of the sam926? and sam9g20 chips. >> * Remove compile time chip dependencies. >> >> Greg Ansley >> >> _______________________________________________ >> 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" >> > From owner-freebsd-arm@FreeBSD.ORG Tue Jul 20 00:11:39 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2ADE2106566B for ; Tue, 20 Jul 2010 00:11:39 +0000 (UTC) (envelope-from yohanes@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id E86808FC12 for ; Tue, 20 Jul 2010 00:11:38 +0000 (UTC) Received: by iwn35 with SMTP id 35so6522032iwn.13 for ; Mon, 19 Jul 2010 17:11:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=joH9236obWsa1+8ZvVhAytZp4z65HshS2myNQYT8h50=; b=vWexPwDSp9pvKfCzr+7UGnWXq1TtIiWAIu0vG6DvEt7cZks9GW+Me/BXl6vH/kpTgp gpm9dwlUmY4xpNHfRvRLBvHUOYIn8ArJ5lUu9CsyfHrhfeiJYoR/M7y38mSUXh3rYlLl 9P6Ehxg+5SXoSmuN+A/Q18ghZDJ6Vw4gpAIf4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=bmGzttjcSy/Sap06ib5m82x2JhkSbQqc8yRXvMpXlIkAvAh5VVNpkg+cImK1tHhhaQ QEXWSkjIRBH6deOBSJP0xWfM6QE+lRiUqI3OkrCDOmKhF2TKETC/FhcvrLwhi2W3/zuh n0MHGGcGjjpPJg2/JmlT7M/plcvJE29EXExTg= Received: by 10.231.170.79 with SMTP id c15mr6285980ibz.82.1279584698130; Mon, 19 Jul 2010 17:11:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.19.197 with HTTP; Mon, 19 Jul 2010 17:11:18 -0700 (PDT) In-Reply-To: <20100719153614.GI28908@cicely7.cicely.de> References: <4C444E8B.6090104@ansley.com> <20100719153614.GI28908@cicely7.cicely.de> From: Yohanes Nugroho Date: Tue, 20 Jul 2010 07:11:18 +0700 Message-ID: To: ticso@cicely.de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-arm@freebsd.org Subject: Re: at91sam9g20: Upcoming Patches X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jul 2010 00:11:39 -0000 On Mon, Jul 19, 2010 at 10:36 PM, Bernd Walter wr= ote: >> if_ate.c: >> >> =C2=A0 =C2=A0* Support for sam9 "EMAC" controller. >> =C2=A0 =C2=A0* Support for rmii interface to phy. > > RM9200 ate requires specific DMA alignment, which required a few > realign copys. > This isn't neccessary for most other AT91 devices and for sure > not with any AT91SAM9x device. > Not sure if all of them are automatically avoided - you might want > to verify the code about this point. > There is also RBNA workaround, which should be RM9200 specifc, > which shouldn't be triggered with others, but you might want to save > a few bytes codespace. And looking at Linux's code, they separate for the RM9200 driver and newer AT9 (macb) drivers. I haven't looked deeply, but it seems that if we are going to support all variations of RM9200 PHY for link checking purpose, there will a lot of RM9200 specific code. I agree that there are many things in common between these two drivers, but I don't know if it is a good idea to keep everything in one file. --=20 Regards Yohanes http://yohan.es/ From owner-freebsd-arm@FreeBSD.ORG Tue Jul 20 00:25:07 2010 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68E601065676 for ; Tue, 20 Jul 2010 00:25:07 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 2BA558FC08 for ; Tue, 20 Jul 2010 00:25:07 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o6K0LYAE050690; Mon, 19 Jul 2010 18:21:35 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 19 Jul 2010 18:22:02 -0600 (MDT) Message-Id: <20100719.182202.918765004097971572.imp@bsdimp.com> To: yohanes@gmail.com From: "M. Warner Losh" In-Reply-To: References: <4C444E8B.6090104@ansley.com> <20100719153614.GI28908@cicely7.cicely.de> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-arm@FreeBSD.org, ticso@cicely.de Subject: Re: at91sam9g20: Upcoming Patches X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jul 2010 00:25:07 -0000 In message: Yohanes Nugroho writes: : On Mon, Jul 19, 2010 at 10:36 PM, Bernd Walter wrote: : >> if_ate.c: : >> : >> =A0 =A0* Support for sam9 "EMAC" controller. : >> =A0 =A0* Support for rmii interface to phy. : > : > RM9200 ate requires specific DMA alignment, which required a few : > realign copys. : > This isn't neccessary for most other AT91 devices and for sure : > not with any AT91SAM9x device. : > Not sure if all of them are automatically avoided - you might want : > to verify the code about this point. : > There is also RBNA workaround, which should be RM9200 specifc, : > which shouldn't be triggered with others, but you might want to sav= e : > a few bytes codespace. : = : And looking at Linux's code, they separate for the RM9200 driver and : newer AT9 (macb) drivers. I haven't looked deeply, but it seems that : if we are going to support all variations of RM9200 PHY for link : checking purpose, there will a lot of RM9200 specific code. Unlike Linux, all that's abstracted out in FreeBSD, so it is easy to support dozens of different PYHs. In fact, I don't think there's any PHY specific code in the current ATE driver... : I agree that there are many things in common between these two : drivers, but I don't know if it is a good idea to keep everything in : one file. Yea, I worry about the performance on newer parts of the older code, which has stinky performance due to hardware limitations. Warner From owner-freebsd-arm@FreeBSD.ORG Tue Jul 20 02:30:43 2010 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C42881065670 for ; Tue, 20 Jul 2010 02:30:43 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 6DBB58FC12 for ; Tue, 20 Jul 2010 02:30:43 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o6K2UcaE076098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Jul 2010 04:30:38 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.3/8.14.3) with ESMTP id o6K2UZGG009396 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jul 2010 04:30:35 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o6K2UZQx034631; Tue, 20 Jul 2010 04:30:35 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o6K2UZWv034630; Tue, 20 Jul 2010 04:30:35 +0200 (CEST) (envelope-from ticso) Date: Tue, 20 Jul 2010 04:30:34 +0200 From: Bernd Walter To: "M. Warner Losh" Message-ID: <20100720023034.GS28908@cicely7.cicely.de> References: <4C444E8B.6090104@ansley.com> <20100719153614.GI28908@cicely7.cicely.de> <20100719.182202.918765004097971572.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20100719.182202.918765004097971572.imp@bsdimp.com> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: freebsd-arm@FreeBSD.org, ticso@cicely.de Subject: Re: at91sam9g20: Upcoming Patches X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2010 02:30:43 -0000 On Mon, Jul 19, 2010 at 06:22:02PM -0600, M. Warner Losh wrote: > In message: > Yohanes Nugroho writes: > : On Mon, Jul 19, 2010 at 10:36 PM, Bernd Walter wrote: > : >> if_ate.c: > : >> > : >>    * Support for sam9 "EMAC" controller. > : >>    * Support for rmii interface to phy. > : > > : > RM9200 ate requires specific DMA alignment, which required a few > : > realign copys. > : > This isn't neccessary for most other AT91 devices and for sure > : > not with any AT91SAM9x device. > : > Not sure if all of them are automatically avoided - you might want > : > to verify the code about this point. > : > There is also RBNA workaround, which should be RM9200 specifc, > : > which shouldn't be triggered with others, but you might want to save > : > a few bytes codespace. > : > : And looking at Linux's code, they separate for the RM9200 driver and > : newer AT9 (macb) drivers. I haven't looked deeply, but it seems that > : if we are going to support all variations of RM9200 PHY for link > : checking purpose, there will a lot of RM9200 specific code. > > Unlike Linux, all that's abstracted out in FreeBSD, so it is easy to > support dozens of different PYHs. In fact, I don't think there's any > PHY specific code in the current ATE driver... No there isn't - at least not with the SAM9260. I know the ATE in SAM7X256/512 very well and beside that some revs of them have broken RMII support it is the same ATE as in SAM9260. > : I agree that there are many things in common between these two > : drivers, but I don't know if it is a good idea to keep everything in > : one file. > > Yea, I worry about the performance on newer parts of the older code, > which has stinky performance due to hardware limitations. The performance has two reasons. First the fact that the RM9200 ATE can't DMA into non 4-byte aligned buffers, which requires copying and memory bandwidth is rather slow, which especially sucks because of the required copy'ing. IP headers are no n*4 bytes, so you want a 2 byte offset in your receive buffers otherwise IP code copy'es received buffers. On sending AFAIK the ATE driver copy'es data into 4 alignment. The memory interface on SAM9 is much faster because it is DDR, higher clocked and with it's bus matrix e.g. DMA can access DDRAM and CPU IO in parallel. I don't see a technical reason to have different source files. A few things can be tuned on compiletime, but this is only a win to save code size - from the runtime point a few rev-checks in hybrid kernel shouldn't hurt. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Tue Jul 20 12:04:58 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 536691065673 for ; Tue, 20 Jul 2010 12:04:58 +0000 (UTC) (envelope-from gja@ansley.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1B3158FC14 for ; Tue, 20 Jul 2010 12:04:57 +0000 (UTC) Received: by gwb19 with SMTP id 19so2683112gwb.13 for ; Tue, 20 Jul 2010 05:04:57 -0700 (PDT) Received: by 10.100.128.13 with SMTP id a13mr6362498and.163.1279627496440; Tue, 20 Jul 2010 05:04:56 -0700 (PDT) Received: from G5.internal.ansley.com (99-135-104-139.lightspeed.tukrga.sbcglobal.net [99.135.104.139]) by mx.google.com with ESMTPS id b17sm74822255anh.25.2010.07.20.05.04.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 20 Jul 2010 05:04:55 -0700 (PDT) Sender: Greg Ansley Message-ID: <4C4590E5.1020407@ansley.com> Date: Tue, 20 Jul 2010 08:04:53 -0400 From: Greg Ansley User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: freebsd-arm@FreeBSD.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Subject: AT91RM9200: USB broken? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jul 2010 12:04:58 -0000 While regression testing my patches, I found that USB is not working on the AT91RM9200 from head (pre-patch). Error shown are the same with or without a USB device attached. Just wondering of anyone has any insights before I spend time going down this rabbit hole... KB920x >go 0x200000e0 ## Starting application at 0x200000E0 ... KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #1: Tue Jul 20 07:49:38 EDT 2010 gja@DL380.internal.ansley.com:/usr/obj/arm.arm/usr/home/gja/freebsd-sam9g20/svn2/sys/KB920X arm CPU: ARM920T rev 0 (ARM9TDMI core) DC enabled IC enabled WB enabled LABT 16KB/32B 64-way Instruction cache 16KB/32B 64-way write-back-locking-A Data cache real memory = 67108864 (64 MB) avail memory = 61509632 (58 MB) atmelarm0: on motherboard at91_st0: mem 0xdffffd00-0xdffffdff irq 1 on atmelarm0 at91_st0: watchdog registered, timeout intervall max. 64 sec at91_pio0: mem 0xdffff400-0xdffff5ff irq 1 on atmelarm0 at91_pio0: ABSR: 0x60 OSR: 0 PSR:0x3f380000 ODSR: 0 at91_pio0: [FILTER] at91_pio1: mem 0xdffff600-0xdffff7ff irq 1 on atmelarm0 at91_pio1: ABSR: 0xff301 OSR: 0x2 PSR:0x3fc00cfe ODSR: 0 at91_pio1: [FILTER] at91_pio2: mem 0xdffff800-0xdffff9ff irq 1 on atmelarm0 at91_pio2: ABSR: 0 OSR: 0x1000000a PSR:0xffffc075 ODSR: 0x10000000 at91_pio2: [FILTER] at91_pio3: mem 0xdffffa00-0xdffffbff irq 1 on atmelarm0 at91_pio3: ABSR: 0 OSR: 0 PSR:0xfffffff ODSR: 0 at91_pio3: [FILTER] at91_pmc0: mem 0xdffffc00-0xdffffcff irq 1 on atmelarm0 at91_pmc0: Primary: 10000000 Hz PLLA: 180 MHz CPU: 180 MHz MCK: 60 MHz at91_mci0: mem 0xdffb4000-0xdffb7fff irq 10 on atmelarm0 at91_mci0: [ITHREAD] mmc0: on at91_mci0 at91_twi0: mem 0xdffb8000-0xdffbbfff irq 12 on atmelarm0 at91_twi0: [ITHREAD] iicbus0: on at91_twi0 setting cwgr to 0x1a4a4 iic0: on iicbus0 icee0: at addr 0xa0 on iicbus0 ate0: mem 0xdffbc000-0xdffbffff irq 24 on atmelarm0 miibus0: on ate0 ukphy0: PHY 0 on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ate0: Ethernet address: 04:00:00:00:00:00 ate0: [ITHREAD] uart0: mem 0xdffff200-0xdffff3ff irq 1 on atmelarm0 uart0: [FILTER]ï¿œuart0: console (115200,n,8,1) uart1: mem 0xdffc0000-0xdffc3fff irq 6 on atmelarm0 uart1: [FILTER] uart2: mem 0xdffc4000-0xdffc7fff irq 7 on atmelarm0 uart2: [FILTER] uart3: mem 0xdffc8000-0xdffcbfff irq 8 on atmelarm0 uart3: [FILTER] uart4: mem 0xdffcc000-0xdffcffff irq 9 on atmelarm0 uart4: [FILTER] spi0: mem 0xdffe0000-0xdffe3fff irq 13 on atmelarm0 spi0: [ITHREAD] spibus0: on spi0 ohci0: mem 0xdfe00000-0xdfefffff irq 23 on atmelarm0 ohci0: [ITHREAD] usbus0 on ohci0 Cannot get 100 Hz clock; using 100Hz at91_st0: [FILTER] Timecounter "AT91RM9200 timer" frequency 32768 Hz quality 1000 Timecounters tick every 10.000 msec usbus0: 12Mbps Full Speed USB v1.0 Root mount waiting for: usbus0 ugen0.1: at usbus0 uhub0: on usbus0 uhub0: 2 ports with 2 removable, self powered Root mount waiting for: usbus0 usb_alloc_device: set address 2 failed (USB_ERR_IOERROR, ignored) usb_alloc_device: getting device descriptor at addr 2 failed, USB_ERR_IOERROR usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored) usbd_req_re_enumerate: getting device descriptor at addr 2 failed, USB_ERR_IOERROR Root mount waiting for: usbus0 usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored) Root mount waiting for: usbus0 usbd_req_re_enumerate: getting device descriptor at addr 2 failed, USB_ERR_IOERROR ugen0.2: <(null)> at usbus0 (disconnected) uhub_reattach_port: could not allocate new device Trying to mount root from ufs:/dev/mmcsd0s1a From owner-freebsd-arm@FreeBSD.ORG Tue Jul 20 12:08:42 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF710106568C for ; Tue, 20 Jul 2010 12:08:42 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe11.swip.net [212.247.155.65]) by mx1.freebsd.org (Postfix) with ESMTP id 2604D8FC12 for ; Tue, 20 Jul 2010 12:08:41 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=54-H3ucdrW8A:10 a=IkcTkHD0fZMA:10 a=M8b_wTzEtboA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=5KR62X8JAAAA:8 a=0kFOGFCJm3w7nv2YeCQA:9 a=jdU--WXyqFDK4PXolKwA:7 a=3c5EHj4XJNScpctUED1YS47TBFkA:4 a=QEXdDO2ut3YA:10 a=WmIdRVL8glqQs9iJ:21 a=3JXxVht94jGjTG-q:21 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe11.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 1243823491; Tue, 20 Jul 2010 14:08:39 +0200 From: Hans Petter Selasky To: freebsd-arm@freebsd.org Date: Tue, 20 Jul 2010 14:05:43 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.1-PRERELEASE; KDE/4.4.5; amd64; ; ) References: <4C4590E5.1020407@ansley.com> In-Reply-To: <4C4590E5.1020407@ansley.com> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'( =?utf-8?q?=3B=5FIjlA=3A=0A=09hGE=2E=2EEw?=, =?utf-8?q?XAQ*o=23=5C/M=7ESC=3DS1-f9=7BEzRfT=27=7CHhll5Q=5Dha5Bt-s=7CoTlKM?= =?utf-8?q?usi=3A1e=5BwJl=7Dkd=7DGR=0A=09Z0adGx-x=5F0zGbZj=27e?=(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201007201405.43686.hselasky@c2i.net> Cc: Subject: Re: AT91RM9200: USB broken? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jul 2010 12:08:42 -0000 On Tuesday 20 July 2010 14:04:53 Greg Ansley wrote: > While regression testing my patches, I found that USB is not working on > the AT91RM9200 from head (pre-patch). Error shown are the same with or > without a USB device attached. >=20 > Just wondering of anyone has any insights before I spend time going down > this rabbit hole... >=20 > KB920x >go 0x200000e0 > ## Starting application at 0x200000E0 ... > KDB: debugger backends: ddb > KDB: current backend: ddb > Copyright (c) 1992-2010 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 9.0-CURRENT #1: Tue Jul 20 07:49:38 EDT 2010 > gja@DL380.internal.ansley.com:/usr/obj/arm.arm/usr/home/gja/freebsd-sam9g= 20 > /svn2/sys/KB920X arm > CPU: ARM920T rev 0 (ARM9TDMI core) > DC enabled IC enabled WB enabled LABT > 16KB/32B 64-way Instruction cache > 16KB/32B 64-way write-back-locking-A Data cache > real memory =3D 67108864 (64 MB) > avail memory =3D 61509632 (58 MB) > atmelarm0: on motherboard > at91_st0: mem 0xdffffd00-0xdffffdff irq 1 on atmelarm0 > at91_st0: watchdog registered, timeout intervall max. 64 sec > at91_pio0: mem 0xdffff400-0xdffff5ff irq 1 on atmelarm0 > at91_pio0: ABSR: 0x60 OSR: 0 PSR:0x3f380000 ODSR: 0 > at91_pio0: [FILTER] > at91_pio1: mem 0xdffff600-0xdffff7ff irq 1 on atmelarm0 > at91_pio1: ABSR: 0xff301 OSR: 0x2 PSR:0x3fc00cfe ODSR: 0 > at91_pio1: [FILTER] > at91_pio2: mem 0xdffff800-0xdffff9ff irq 1 on atmelarm0 > at91_pio2: ABSR: 0 OSR: 0x1000000a PSR:0xffffc075 ODSR: 0x10000000 > at91_pio2: [FILTER] > at91_pio3: mem 0xdffffa00-0xdffffbff irq 1 on atmelarm0 > at91_pio3: ABSR: 0 OSR: 0 PSR:0xfffffff ODSR: 0 > at91_pio3: [FILTER] > at91_pmc0: mem 0xdffffc00-0xdffffcff irq 1 on atmelarm0 > at91_pmc0: Primary: 10000000 Hz PLLA: 180 MHz CPU: 180 MHz MCK: 60 MHz > at91_mci0: mem 0xdffb4000-0xdffb7fff irq 10 on > atmelarm0 > at91_mci0: [ITHREAD] > mmc0: on at91_mci0 > at91_twi0: mem 0xdffb8000-0xdffbbfff irq 12 on atmelarm0 > at91_twi0: [ITHREAD] > iicbus0: on at91_twi0 > setting cwgr to 0x1a4a4 > iic0: on iicbus0 > icee0: at addr 0xa0 on iicbus0 > ate0: mem 0xdffbc000-0xdffbffff irq 24 on atmelarm0 > miibus0: on ate0 > ukphy0: PHY 0 on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ate0: Ethernet address: 04:00:00:00:00:00 > ate0: [ITHREAD] > uart0: mem 0xdffff200-0xdffff3ff irq 1 on atmelarm0 > uart0: [FILTER]=EF=BF=BDuart0: console (115200,n,8,1) > uart1: mem 0xdffc0000-0xdffc3fff irq 6 on atmelarm0 > uart1: [FILTER] > uart2: mem 0xdffc4000-0xdffc7fff irq 7 on atmelarm0 > uart2: [FILTER] > uart3: mem 0xdffc8000-0xdffcbfff irq 8 on atmelarm0 > uart3: [FILTER] > uart4: mem 0xdffcc000-0xdffcffff irq 9 on atmelarm0 > uart4: [FILTER] > spi0: mem 0xdffe0000-0xdffe3fff irq 13 on atmelarm0 > spi0: [ITHREAD] > spibus0: on spi0 > ohci0: mem 0xdfe00000-0xdfefffff irq > 23 on atmelarm0 > ohci0: [ITHREAD] > usbus0 on ohci0 > Cannot get 100 Hz clock; using 100Hz > at91_st0: [FILTER] > Timecounter "AT91RM9200 timer" frequency 32768 Hz quality 1000 > Timecounters tick every 10.000 msec > usbus0: 12Mbps Full Speed USB v1.0 > Root mount waiting for: usbus0 > ugen0.1: at usbus0 > uhub0: on usbus0 > uhub0: 2 ports with 2 removable, self powered > Root mount waiting for: usbus0 > usb_alloc_device: set address 2 failed (USB_ERR_IOERROR, ignored) > usb_alloc_device: getting device descriptor at addr 2 failed, > USB_ERR_IOERROR > usbd_req_re_enumerate: addr=3D2, set address failed! (USB_ERR_IOERROR, > ignored) > usbd_req_re_enumerate: getting device descriptor at addr 2 failed, > USB_ERR_IOERROR > Root mount waiting for: usbus0 > usbd_req_re_enumerate: addr=3D2, set address failed! (USB_ERR_IOERROR, > ignored) > Root mount waiting for: usbus0 > usbd_req_re_enumerate: getting device descriptor at addr 2 failed, > USB_ERR_IOERROR > ugen0.2: <(null)> at usbus0 (disconnected) > uhub_reattach_port: could not allocate new device > Trying to mount root from ufs:/dev/mmcsd0s1a >=20 Hi, I think those messages are normal, because one of the USB ports is not=20 connected. What messages do you get when plugging in a real USB device? =2D-HPS From owner-freebsd-arm@FreeBSD.ORG Tue Jul 20 13:28:34 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DAB01065670 for ; Tue, 20 Jul 2010 13:28:34 +0000 (UTC) (envelope-from gja@ansley.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id AC1B58FC12 for ; Tue, 20 Jul 2010 13:28:30 +0000 (UTC) Received: by gwb19 with SMTP id 19so2761275gwb.13 for ; Tue, 20 Jul 2010 06:28:29 -0700 (PDT) Received: by 10.100.122.12 with SMTP id u12mr796469anc.112.1279632509546; Tue, 20 Jul 2010 06:28:29 -0700 (PDT) Received: from G5.internal.ansley.com (99-135-104-139.lightspeed.tukrga.sbcglobal.net [99.135.104.139]) by mx.google.com with ESMTPS id u14sm75263904ann.0.2010.07.20.06.28.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 20 Jul 2010 06:28:28 -0700 (PDT) Sender: Greg Ansley Message-ID: <4C45A47A.8070403@ansley.com> Date: Tue, 20 Jul 2010 09:28:26 -0400 From: Greg Ansley User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: "freebsd-arm@FreeBSD.org" References: <4C4590E5.1020407@ansley.com> <201007201405.43686.hselasky@c2i.net> In-Reply-To: <201007201405.43686.hselasky@c2i.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: AT91RM9200: USB broken? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jul 2010 13:28:34 -0000 No, I don't think this is normal. The messages are exactly the same with a known good USB flash drive attached, and the drive is not found. Same result as far back as 8.0-RELEASE-p4. Since USB works fine on the SAM9G20 card I think I will ignore this for now, so as not to delay what I am doing. Greg On 7/20/10 8:05 AM, Hans Petter Selasky wrote: > On Tuesday 20 July 2010 14:04:53 Greg Ansley wrote: > >> While regression testing my patches, I found that USB is not working on >> the AT91RM9200 from head (pre-patch). Error shown are the same with or >> without a USB device attached. >> >> Just wondering of anyone has any insights before I spend time going down >> this rabbit hole... >> >> ... >> usbus0: 12Mbps Full Speed USB v1.0 >> Root mount waiting for: usbus0 >> ugen0.1: at usbus0 >> uhub0: on usbus0 >> uhub0: 2 ports with 2 removable, self powered >> Root mount waiting for: usbus0 >> usb_alloc_device: set address 2 failed (USB_ERR_IOERROR, ignored) >> usb_alloc_device: getting device descriptor at addr 2 failed, >> USB_ERR_IOERROR >> usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, >> ignored) >> usbd_req_re_enumerate: getting device descriptor at addr 2 failed, >> USB_ERR_IOERROR >> Root mount waiting for: usbus0 >> usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, >> ignored) >> Root mount waiting for: usbus0 >> usbd_req_re_enumerate: getting device descriptor at addr 2 failed, >> USB_ERR_IOERROR >> ugen0.2:<(null)> at usbus0 (disconnected) >> uhub_reattach_port: could not allocate new device >> Trying to mount root from ufs:/dev/mmcsd0s1a >> >> > Hi, > > I think those messages are normal, because one of the USB ports is not > connected. > > What messages do you get when plugging in a real USB device? > > --HPS > From owner-freebsd-arm@FreeBSD.ORG Tue Jul 20 13:59:05 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 812351065670 for ; Tue, 20 Jul 2010 13:59:05 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 108188FC15 for ; Tue, 20 Jul 2010 13:59:04 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o6KDx1Ih012181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Jul 2010 15:59:01 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.3/8.14.3) with ESMTP id o6KDwwCn029549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jul 2010 15:58:58 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o6KDwwTX037687; Tue, 20 Jul 2010 15:58:58 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o6KDwwdp037686; Tue, 20 Jul 2010 15:58:58 +0200 (CEST) (envelope-from ticso) Date: Tue, 20 Jul 2010 15:58:58 +0200 From: Bernd Walter To: Greg Ansley Message-ID: <20100720135858.GA28908@cicely7.cicely.de> References: <4C4590E5.1020407@ansley.com> <201007201405.43686.hselasky@c2i.net> <4C45A47A.8070403@ansley.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C45A47A.8070403@ansley.com> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: "freebsd-arm@FreeBSD.org" Subject: Re: AT91RM9200: USB broken? X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2010 13:59:05 -0000 On Tue, Jul 20, 2010 at 09:28:26AM -0400, Greg Ansley wrote: > No, I don't think this is normal. The messages are exactly the same with > a known good USB flash drive attached, and the drive is not found. Those _are_ normal for RM9200 in QFP-208. The RM9200 has two USB ports - both of them are bonded in the BGA version and works fine there. In QFP case however only one is bonded and the second port can't be terminated properly. There is an errata in the datasheet about this. Since it is impossible to find out via software which RM9200 you have we can't just ignore the secondary port - maybe as a compile time option, but not for a generic kernel. The latest current I tested on RM9200 was svn-rev 204418 and USB was working fine - including those error messages for the faulty secondary port. So it looks like your device isn't noticed as being connected at all, which is a bit strange because your error messages clearly show that it got the faulty device connected from the secondary port. Did it ever work for you? If yes - did you try it with the same USB device? Do you have an RM9200 in BGA or QFP soldered on your board? > Same result as far back as 8.0-RELEASE-p4. Since USB works fine on the > SAM9G20 card I think I will ignore this for now, so as not to delay what > I am doing. > > Greg > > On 7/20/10 8:05 AM, Hans Petter Selasky wrote: > >On Tuesday 20 July 2010 14:04:53 Greg Ansley wrote: > > > >>While regression testing my patches, I found that USB is not working on > >>the AT91RM9200 from head (pre-patch). Error shown are the same with or > >>without a USB device attached. > >> > >>Just wondering of anyone has any insights before I spend time going down > >>this rabbit hole... > >> > >>... > >>usbus0: 12Mbps Full Speed USB v1.0 > >>Root mount waiting for: usbus0 > >>ugen0.1: at usbus0 > >>uhub0: on usbus0 > >>uhub0: 2 ports with 2 removable, self powered > >>Root mount waiting for: usbus0 > >>usb_alloc_device: set address 2 failed (USB_ERR_IOERROR, ignored) > >>usb_alloc_device: getting device descriptor at addr 2 failed, > >>USB_ERR_IOERROR > >>usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, > >>ignored) > >>usbd_req_re_enumerate: getting device descriptor at addr 2 failed, > >>USB_ERR_IOERROR > >>Root mount waiting for: usbus0 > >>usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, > >>ignored) > >>Root mount waiting for: usbus0 > >>usbd_req_re_enumerate: getting device descriptor at addr 2 failed, > >>USB_ERR_IOERROR > >>ugen0.2:<(null)> at usbus0 (disconnected) > >>uhub_reattach_port: could not allocate new device > >>Trying to mount root from ufs:/dev/mmcsd0s1a > >> > >> > >Hi, > > > >I think those messages are normal, because one of the USB ports is not > >connected. > > > >What messages do you get when plugging in a real USB device? > > > >--HPS > > > _______________________________________________ > 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" -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Tue Jul 20 15:37:24 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 780ED1065677 for ; Tue, 20 Jul 2010 15:37:24 +0000 (UTC) (envelope-from gja@ansley.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3A94E8FC16 for ; Tue, 20 Jul 2010 15:37:23 +0000 (UTC) Received: by gwb19 with SMTP id 19so2906572gwb.13 for ; Tue, 20 Jul 2010 08:37:23 -0700 (PDT) Received: by 10.101.144.11 with SMTP id w11mr6712608ann.236.1279640242967; Tue, 20 Jul 2010 08:37:22 -0700 (PDT) Received: from G5.internal.ansley.com (99-135-104-139.lightspeed.tukrga.sbcglobal.net [99.135.104.139]) by mx.google.com with ESMTPS id 14sm75826757ant.21.2010.07.20.08.37.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 20 Jul 2010 08:37:22 -0700 (PDT) Sender: Greg Ansley Message-ID: <4C45C2AF.9030608@ansley.com> Date: Tue, 20 Jul 2010 11:37:19 -0400 From: Greg Ansley User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: ticso@cicely.de References: <4C4590E5.1020407@ansley.com> <201007201405.43686.hselasky@c2i.net> <4C45A47A.8070403@ansley.com> <20100720135858.GA28908@cicely7.cicely.de> In-Reply-To: <20100720135858.GA28908@cicely7.cicely.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@FreeBSD.org" , Bernd Walter Subject: Re: AT91RM9200: USB broken? No! X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jul 2010 15:37:24 -0000 It's a QFP so the errors are OK. Turned out to be a bad solder joint on pin 1 of the USB connector (power). Connector on this card is not very mechanically stable with the mounting posts going into huge worthless holes. :-( Error messages were just a red herring, after not having seen them for weeks while working on the SAM9G20. Greg On 7/20/10 9:58 AM, Bernd Walter wrote: > So it looks like your device isn't noticed as being connected at all, > which is a bit strange because your error messages clearly show that > it got the faulty device connected from the secondary port. > > From owner-freebsd-arm@FreeBSD.ORG Tue Jul 20 17:03:45 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3AA01065670 for ; Tue, 20 Jul 2010 17:03:45 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 14B658FC18 for ; Tue, 20 Jul 2010 17:03:44 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o6KH3fSZ023925 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Jul 2010 19:03:41 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.3/8.14.3) with ESMTP id o6KH3dKW034880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jul 2010 19:03:39 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o6KH3dUE038503; Tue, 20 Jul 2010 19:03:39 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o6KH3bOq038502; Tue, 20 Jul 2010 19:03:37 +0200 (CEST) (envelope-from ticso) Date: Tue, 20 Jul 2010 19:03:37 +0200 From: Bernd Walter To: Greg Ansley Message-ID: <20100720170337.GB28908@cicely7.cicely.de> References: <4C4590E5.1020407@ansley.com> <201007201405.43686.hselasky@c2i.net> <4C45A47A.8070403@ansley.com> <20100720135858.GA28908@cicely7.cicely.de> <4C45C2AF.9030608@ansley.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C45C2AF.9030608@ansley.com> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-1.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, PLING_QUERY=0.994, T_RP_MATCHES_RCVD=-0.01 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: "freebsd-arm@FreeBSD.org" , Bernd Walter , ticso@cicely.de Subject: Re: AT91RM9200: USB broken? No! X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2010 17:03:45 -0000 On Tue, Jul 20, 2010 at 11:37:19AM -0400, Greg Ansley wrote: > It's a QFP so the errors are OK. > > Turned out to be a bad solder joint on pin 1 of the USB connector > (power). Connector on this card is not very mechanically stable with the > mounting posts going into huge worthless holes. :-( That makes sense. A device pulls up one of the data line up to 3.3V with a 1.5k Ohm resistor to show presense. A bus powered device however can't do this without having power and a self powered device isn't allowd to supply current into data wires without sensing the 5V, although many self powered devices violate this rule. So in fact a few self powered devices might function without 5V from USB, although they are not allowed to. > Error messages were just a red herring, after not having seen them for > weeks while working on the SAM9G20. > > Greg > > On 7/20/10 9:58 AM, Bernd Walter wrote: > >So it looks like your device isn't noticed as being connected at all, > >which is a bit strange because your error messages clearly show that > >it got the faulty device connected from the secondary port. > > > > > _______________________________________________ > 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" -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Tue Jul 20 17:10:42 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D541106566B; Tue, 20 Jul 2010 17:10:42 +0000 (UTC) (envelope-from marktinguely@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 041318FC14; Tue, 20 Jul 2010 17:10:41 +0000 (UTC) Received: by gwb19 with SMTP id 19so3012595gwb.13 for ; Tue, 20 Jul 2010 10:10:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:content-type :content-transfer-encoding; bh=dKnCJPM0gWy6viym9dAwJiS5D6RYY8CHS0XG/MhCZq4=; b=mCAEofPOeKAE/RmOop0xysVOgSb0U8tSz9yvqM1Sj8T+Ahm6Oqbp4xctrpjf2T87HB IoBQxekfqDX7RkNuJGwMDGPemJ7MLEZRlIiSBf3O0y2jnLxCAJyFEE9ufde8A3KGmjX3 WiG7MQ4Wxh0TmunTicrTYLKlgoNdnl8wFbN/8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type:content-transfer-encoding; b=mLFYKg1HB0NevRUUjIgRH+YUf9lsVqVgjmFx9/cnZARcFKQRc2/CrmID/qgUtUmlH7 zL7F1VkdBqHnibHpZ+YKtc1pHiNYeXM8OYxVMQWXkJTX6eohjMpkvLSdY35Uk/EfSxkC sRMkm390eQOGCeUlNCXejwQMV9N/qNE4K8LwU= Received: by 10.150.208.1 with SMTP id f1mr642361ybg.331.1279645838244; Tue, 20 Jul 2010 10:10:38 -0700 (PDT) Received: from [192.168.0.3] (71-38-48-15.frgo.qwest.net [71.38.48.15]) by mx.google.com with ESMTPS id e8sm27759384ibb.20.2010.07.20.10.10.37 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 20 Jul 2010 10:10:37 -0700 (PDT) Message-ID: <4C45D88A.30107@gmail.com> Date: Tue, 20 Jul 2010 12:10:34 -0500 From: Mark Tinguely User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org Subject: Revision 209887 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jul 2010 17:10:42 -0000 This is a FYI on the pmap_qenter() change in the i386/amd64 - revision 209887. PS to last week's email. Sorry I did not keep the message-id consistent. A similar change in the ARM pmap_kenter_internal() seems to help significantly. Running a port (bash3) compile on a modified GUMSTIX kernel on an emulator, I am getting mid-teen percentages of mapping request that we do not have to do. An example snapshot of the counts: 2475 kenter()s not needed. 11479 enters required. All 11479 old ptes were zero because we aggressively remove dangling allocation. As the compilation continues, the ratio between kenter()s not needed per kenters() needed goes up. The numbers above assume a patch for vfs_unbusy_pages() that is the duplicate to the one in bufdone_finish(). In theory the vfs_unbusy_pages() should help keep the number of unnecessary pmap_qenter() calls down, so the above numbers could only be higher without that patch. I also propose to removed the calls to pmap_wb_page() in pmap_qenter() and pmap_inv_page() in pmap_qremove(): In pmap_qenter(), pmap_fix_cache() will write back the page mappings and turn off caching if shared. If the page was shared when pmap_qremove() is called, the caches will already be turned off, and pmap_kremove() will writeback and invalidate this mapping during the removal process. --Mark. From owner-freebsd-arm@FreeBSD.ORG Tue Jul 20 17:36:05 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DC1B106566B; Tue, 20 Jul 2010 17:36:05 +0000 (UTC) (envelope-from alc@cs.rice.edu) Received: from mail.cs.rice.edu (mail.cs.rice.edu [128.42.1.31]) by mx1.freebsd.org (Postfix) with ESMTP id 072918FC1A; Tue, 20 Jul 2010 17:36:04 +0000 (UTC) Received: from mail.cs.rice.edu (localhost.localdomain [127.0.0.1]) by mail.cs.rice.edu (Postfix) with ESMTP id 9929A2C2B6E; Tue, 20 Jul 2010 12:36:04 -0500 (CDT) X-Virus-Scanned: by amavis-2.4.0 at mail.cs.rice.edu Received: from mail.cs.rice.edu ([127.0.0.1]) by mail.cs.rice.edu (mail.cs.rice.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ipPg3qEZY4WE; Tue, 20 Jul 2010 12:35:56 -0500 (CDT) Received: from adsl-216-63-78-18.dsl.hstntx.swbell.net (adsl-216-63-78-18.dsl.hstntx.swbell.net [216.63.78.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cs.rice.edu (Postfix) with ESMTP id AA82A2C2B32; Tue, 20 Jul 2010 12:35:56 -0500 (CDT) Message-ID: <4C45DE7C.5080207@cs.rice.edu> Date: Tue, 20 Jul 2010 12:35:56 -0500 From: Alan Cox User-Agent: Thunderbird 2.0.0.24 (X11/20100501) MIME-Version: 1.0 To: Mark Tinguely References: <4C45D88A.30107@gmail.com> In-Reply-To: <4C45D88A.30107@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, freebsd-arm@freebsd.org Subject: Re: Revision 209887 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jul 2010 17:36:05 -0000 Mark Tinguely wrote: > This is a FYI on the pmap_qenter() change in the i386/amd64 - revision > 209887. > PS to last week's email. Sorry I did not keep the message-id consistent. > > A similar change in the ARM pmap_kenter_internal() seems to help > significantly. Running a port (bash3) compile on a modified GUMSTIX > kernel on an emulator, I am getting mid-teen percentages of mapping > request that we do not have to do. An example snapshot of the counts: > > 2475 kenter()s not needed. > 11479 enters required. > All 11479 old ptes were zero because we aggressively remove > dangling allocation. > > As the compilation continues, the ratio between kenter()s not needed > per kenters() needed goes up. > > The numbers above assume a patch for vfs_unbusy_pages() that is the > duplicate to the one in bufdone_finish(). In theory the > vfs_unbusy_pages() should help keep the number of unnecessary > pmap_qenter() calls down, so the above numbers could only be higher > without that patch. > Keep in mind that vfs_unbusy_pages() is only used by the NFS client code, so it may not affect your particular test anyway. > I also propose to removed the calls to pmap_wb_page() in pmap_qenter() > and pmap_inv_page() in pmap_qremove(): > In pmap_qenter(), pmap_fix_cache() will write back the page mappings > and turn off caching if shared. > If the page was shared when pmap_qremove() is called, the caches will > already be turned off, and pmap_kremove() will writeback and > invalidate this mapping during the removal process. > Alan