summaryrefslogtreecommitdiffstats
path: root/sys/mips/conf
Commit message (Collapse)AuthorAgeFilesLines
* Don't hardcode paths to MFS_IMAGE in the kernel config. When they don'tbrooks2012-09-052-2/+0
| | | | | | exist they don't cause "make tinderbox" to fail. Reported by: jhb
* The DIR-825 cal data is in an odd spot. I don't know why it's here.adrian2012-08-301-3/+6
| | | | | (This works on my board because I wrote new caldata into this spot; but this obviously won't work for stock DIR-825 units out there.)
* More attempts at space saving.adrian2012-08-291-2/+4
| | | | | | * add cam as a module to build - but build in scbus/da for now, as "cam" as a module includes all cam devices. Hardly space saving. * Don't build FFS snapshot support.
* Bring over a configuration for the Atheros AP91 reference board.adrian2012-08-292-0/+167
| | | | | | | | This has an AR7240 SoC with an AR9285 wireless NIC on-board. Since the kernel partition on the 4MiB flash is 960KiB, quite a bit is disabled to try and squeeze the build into that. Even lzma'ed, it's still quite large.
* * Don't compile in sysctl descriptionsadrian2012-08-281-1/+4
| | | | * random is fine as a module
* oops, make cfg read-write.adrian2012-08-281-1/+1
|
* This is an initial board configuration for the D-Link DIR-825 dual-bandadrian2012-08-282-0/+135
| | | | | | | | | | | | | | | | | | | | | | | 802.11n router. The flash layout defaults to a 1 MiB section for the kernel so I'm trying very hard to squeeze a minimialistic (LZMA compressde) kernel image into that. I've verified that it boots through to single user mode fine. Issues: * USB doesn't yet work as a module - I need to add something else to the USB AR71xx build before that will work. * There's no switch PHY support - but for now it quite happily behaves as a useful dumb switch out of the box. Phew. * Since a previous flash attempt trashed my radio configuration block, I haven't yet verified whether the wireless works correctly. I'll test that out shortly (read: once I re-calibrate the board somehow.) Thanks to ray@ and the zrouter project for doing some of the initial hard work in figuring out how to bring this board up.
* Convert AP93 to use the new AR724X_BASE configuration file.adrian2012-08-272-166/+24
|
* Slim down the default AR724X build.adrian2012-08-271-28/+30
| | | | The AR724X boards tend to come with minimal RAM/flash.
* Convert to using ulzma.adrian2012-08-271-5/+3
|
* Expose DE4 buttons and switches via a de4bsw device, implemented usingrwatson2012-08-261-1/+11
| | | | | | | | | altera_avgen(4). Fix white space nit that must have arisen during the merge from Perforce. Submitted by: brooks Sponsored by: DARPA, AFRL
* Add terasic_de4led, a led(4) driver for the on-board 8-element LED on therwatson2012-08-263-0/+10
| | | | | | | | | | Terasic DE-4 board. Allow LED configuration to be set using loader tunables, not just from userspace, and preconfigure LED 8 as a kernel heartbeat. For now, this is a Nexus-attached, BERI-only driver, but it could be used with other hard and soft cores on Altera FPGAs as well, in principle. Sponsored by: DARPA, AFRL
* Create a skeleton AR724x SoC board configuration for use by AR724x devices.adrian2012-08-262-0/+191
|
* Add terasic_mtl(4), a device driver for the Terasic Multi-Touch LCD,rwatson2012-08-253-2/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | used with Terasic's DE-4 and other similar FPGA boards. This display is 800x480 and includes a capacitive touch screen, multi-touch gesture recognition, etc. This device driver depends on a Cambridge- provided IP core that allows the MTL device to be hooked up to the Altera Avalon SoC bus, and also provides a VGA-like text frame buffer. Although it is compiled as a single device driver, it actually implements a number of different device nodes exporting various aspects of this multi-function device to userspace: - Simple memory-mapped driver for the MTL 24-bit pixel frame buffer. - Simple memory-mapped driver for the MTL control register set. - Simple memory-mapped driver for the MTL text frame buffer. - syscons attachment for the MTL text frame buffer. This driver attaches directly to Nexus as is common for SoC device drivers, and for the time being is considered BERI-specific, although in principle it might be used with other hard and soft cores on Altera FPGAs. Control registers, including touchscreen input, are simply memory mapped; in the future it would be desirable to hook up a more conventional device node that can stream events, support kqueue(2)/ poll(2)/select(2), etc. This is the first use of syscons on MIPS, as far as I can tell, and there are some loose ends, such as an inability to use the hardware cursor. More fundamentally, it appears that syscons(4) assumes that either a host is PC-like (i386, amd64) *or* it must be using a graphical frame buffer. While the MTL supports a graphical frame buffer, using the text frame buffer is preferable for console use. Fixing this issue in syscons(4) requires non-trivial changes, as the text frame buffer support assumes that direct memory access can be done to the text frame buffer without using bus accessor methods, which is not the case on MIPS. As a workaround for this, we instead double-buffer and pretend to be a graphical frame buffer exposing text accessor methods, leading to some quirks in syscons behaviour. Sponsored by: DARPA, AFRL
* Add isf(4), a driver for the Intel StrataFlash family of NOR flash parts.brooks2012-08-253-0/+12
| | | | | | | | | | | The driver attempts to support all documented parts, but has only been tested with the 512Mbit part on the Terasic DE4 FPGA board. It should be trivial to adapt the driver's attach routine to other embedded boards using with any parts in the family. Also import isfctl(8) which can be used to erase sections of the flash. Sponsored by: DARPA, AFRL
* Don't include syscons in the config just yet. We haven't imported thebrooks2012-08-252-2/+2
| | | | touchscreen driver yet.
* Add reference kernel configurations for FreeBSD/beri in simulation, on therwatson2012-08-257-0/+281
| | | | | | Terasic DE-4, and Terasic tPad Altera-based boards. Sponsored by: DARPA, AFRL
* Remove duplicated GEOM_PART_* options.ray2012-08-238-16/+0
| | | | | PR: 170931 Approved by: adrian
* MFprojects/zfsd:mav2012-05-241-1/+1
| | | | Generalize and unify ses device description.
* Enable the AR8316 switch on the routerstation pro board.adrian2012-05-192-4/+27
| | | | | | | | | | The configuration is: * RGMII, both ports * arge0 - connected to PHY4 as a dedicated port (CPU port) * arge1 - connected to the switch ports I've verified this on my routerstation pro board.
* Remove duplicate config bits.adrian2012-05-121-4/+0
| | | | Submitted by: juli
* Revert this - I disabled it whilst hwpmc is/was broken.adrian2012-05-121-1/+1
|
* Flip on WN1043ND switch PHY support.adrian2012-05-123-5/+35
| | | | | | | | * Add the i2c bitbang bus; * Add the etherswitch/rtl8366rb drivers; * "fix" the USB GPIO configuration so USB actually works. Submitted by: Stefan Bethke <stb@lassitu.de>
* Now that there's a hint for it, add a "I'm an AR7240 switch!" hint.adrian2012-05-121-3/+2
|
* Add in the AP93 configuration file.adrian2012-05-122-0/+335
| | | | | | | | | | | | | | | | | | | The AP93 has: * AR7240 - mips24k processor with integrated 10/100 switch and various other peripherals; * AR9283 - 2x2 2.4GHz 802.11n (with calibration data in flash); * 64MB RAM; * 16MB SPI flash. The switch code detects as an AR8216 at the present moment, which isn't _entirely_ strictly true. However, the MII/MDIO routing in AP93.hints works - the arge0 MAC connects to PHY4 in the switch, but via the switch internal MDIO bus. The switch connects to arge0's MDIO bus, but only to export the switch registers. Thanks to stb and ray for the switch work, and ray for helping determine what the correct switch hints should be for this thing.
* Add switch support to AP96.adrian2012-05-112-10/+9
|
* Add basic SMP support for GXemul. Ideally we would have some way to overridejmallett2012-05-071-0/+3
| | | | | | some of the IPI mechanisms used by the common MIPS SMP code so we could use the multicast IPI facilities, on GXemul as well as on several real hardware platforms, and the ability to have multiple hard IPI types.
* Add a trivial driver for the GXemul Ethernet device. Probably quite buggy andjmallett2012-05-071-3/+17
| | | | | | certainly non-optimal, but enough for basic networking use. Requested by: rwatson
* Add a driver for the GXemul test machine's disk controller and disk devices.jmallett2012-05-061-8/+2
| | | | | | Prefer it to using an md device in the GXEMUL kernel configuration. Requested by: rwatson, theraven
* In the new world order, multiphy is now when the phymask is 0x0.adrian2012-05-031-1/+2
| | | | This makes the TP-WN1043ND (ar913x based) work again.
* mips/mips64eb became mips/mips64 while I wasn't looking (whoops), so updaterwatson2012-05-021-1/+1
| | | | | | | GXEMUL kernel config for the new world order. Spotted by: bz MFC after: 3 weeks
* Merge a rudimentary gxemul "oldtestmips" port. This consists almostrwatson2012-05-022-0/+53
| | | | | | | | | | | | | | | | | | | | | | entirely of one machdep file lifted from the MALTA port, as well as a low-level console and tty driver for the gxemul debugging console device (the emulators stdio). As with many low-level embedded and hypervisor console devices, it is polled only, so we drive TTY I/O from a callout; we are perhaps a bit too aware of the MIPS physical maps in order to attach the console before newbus comes to life. The sample kernel configuration depends on an MD-based root file system, which is not provided. However, any 64-bit, big-endian userspace image (such as one generated for MALTA) should work. This will hopefully be supplemented by additional device drivers for gxemul-specific hardware simulations from Juli Mallett. We have found oldtestmips quite useful for testing and improving aspects of the MIPS port, so it's worth supporting better in FreeBSD. Requested by: theraven, jmallett Sponsored by: DARPA, AFRL MFC after: 3 weeks
* Disable the pll_1000 hint for now, the upcoming work enables it and itadrian2012-05-021-1/+1
| | | | breaks without the switch PHY code.
* * Force the ethernet MII configuration to be RGMIIadrian2012-05-021-3/+3
| | | | | | | * Populate the "pll_1000" field, which will soon be used to override the PLL configuration from the default value. Obtained from: Linux OpenWRT
* Convert AP96 to use the mdioproxy and ARGE_MDIO option.adrian2012-05-012-0/+22
| | | | | | arge1 still works (it's the standalone PHY) but arge0 and the other switch ports don't work. They're enumerated though, demonstrating that the mdiobus abstraction is correctly working.
* Add in the AP96 phy configuration from openwrt.adrian2012-04-151-10/+8
| | | | | | | | | | | | | | * arge0 doesn't (yet) work via the switch PHY ports; I'm not sure why. * arge1 maps to the WAN port. That works. TODO: * The PLL register needs a different (non-default) value for Gigabit Ethernet. The board setup code needs to be extended a bit to allow for non-default pll_1000 values - right now, those values come out of hard-coded values in the per-chip set_pll_ge() routines. Obtained from: Linux / OpenWRT
* Flesh out the rest of the AP96 board/config.adrian2012-04-132-8/+64
|
* * Enable ATH_EEPROM_FIRMWARE, now that it's a compile time optionadrian2012-04-132-4/+6
| | | | * Tidy up things a bit.
* These are uboot, so mark them as such or booting from flash will not work.adrian2012-04-132-0/+4
|
* Introduce configuration files for AP94 and AP96.adrian2012-04-134-0/+120
| | | | | | | | | | | | This uses the new firmware(9) method for squirreling away the EEPROM contents from SPI flash so ath(4) can get to them later. It won't work out of the box just yet - you have to add this to if_ath_pci.c: #define ATH_EEPROM_FIRMWARE .. until I've added it as a configuration option and updated things.
* Assume a big-endian default on MIPS and drop the "eb" suffix from MACHINE_ARCH.jmallett2012-03-2912-12/+12
| | | | | | | | | | | | | | | This makes our naming scheme more closely match other systems and the expectations of much third-party software. MIPS builds which are little-endian should require and exhibit no changes. Big-endian TARGET_ARCHes must be changed: From: To: mipseb mips mipsn32eb mipsn32 mips64eb mips64 An entry has been added to UPDATING and some foot-shooting protection (complete with warnings which should become errors in the near future) to the top-level base system Makefile.
* Resource allocation for XLP SoC SDHCI slotsjchandra2012-03-271-0/+5
| | | | | | | | The on-chip SD slots do not have PCI BARs corresponding to them, so this has to be handled in the custom SoC memory allocation. Provide memory resource for rids corresponding to BAR 0 and 1 in the custom allocation code.
* NOR flash driver for XLP.jchandra2012-03-271-0/+4
| | | | | The NOR interface on the SoC appears on the top level PCI bus. Add a simple driver for this.
* xlpge : driver for XLP network acceleratorjchandra2012-03-271-0/+1
| | | | | | | | | | | | | Features: - network driver for the four 10G interfaces and two management ports on XLP 8xx. - Support 4xx and 3xx variants of the processor. - Source code and firmware building for the 16 mips32r2 micro-code engines in the Network Accelerator. - Basic initialization code for Packet ordering Engine. Submitted by: Prabhath Raman (prabhath at netlogicmicro com) [refactored and fixed up for style by jchandra]
* Opencrypto driver for XLP Security and RSA/ECC blocksjchandra2012-03-271-0/+10
| | | | | | | | Support for the Security and RSA blocks on XLP SoC. Even though the XLP supports many more algorithms, only the ones supported in OCF have been added. Submitted by: Venkatesh J. V. (venkatesh at netlogicmicro com)
* I2C support for XLP, add hints for I2C devices and update PCI resourcejchandra2012-03-272-3/+17
| | | | allocation code.
* Remove pty(4) from our kernel configurations.ed2012-03-216-6/+0
| | | | | | | | | | | As of FreeBSD 8, this driver should not be used. Applications that use posix_openpt(2) and openpty(3) use the pts(4) that is built into the kernel unconditionally. If it turns out high profile depend on the pty(4) module anyway, I'd rather get those fixed. So please report any issues to me. The pty(4) module is still available as a kernel module of course, so a simple `kldload pty' can be used to run old-style pseudo-terminals.
* Don't build kernel.tramp on Octeon. Probably building it should be opt-injmallett2012-03-131-0/+3
| | | | | not opt-out, but I don't know enough about which ports need it to get the defaults right.
* Remove TARGET_BIG_ENDIAN which should have been removed previously.jmallett2012-03-121-1/+0
|
* o) Use ABI, not ISA_* options, to determine whether to compile bits if libkernjmallett2012-03-1213-18/+0
| | | | | | | required for the ABI the kernel is being built for. XXX This is implemented in a kind-of nasty way that involves including source files, but it's still an improvement. o) Retire ISA_* options since they're unused and were always wrong.
OpenPOWER on IntegriCloud