lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1302639810.14216.57.camel@dev.znau.edu.ua>
Date:	Tue, 12 Apr 2011 23:23:30 +0300
From:	George Kashperko <george@...u.edu.ua>
To:	Hauke Mehrtens <hauke@...ke-m.de>
Cc:	balbi@...com, linux-wireless@...r.kernel.org,
	"John W. Linville" <linville@...driver.com>,
	b43-dev@...ts.infradead.org,
	Michael Büsch <mb@...sch.de>,
	Larry Finger <Larry.Finger@...inger.net>,
	Arend van Spriel <arend@...adcom.com>,
	linux-arm-kernel@...ts.infradead.org,
	Russell King <rmk@....linux.org.uk>,
	Arnd Bergmann <arnd@...db.de>,
	Andy Botting <andy@...ybotting.com>,
	linuxdriverproject <devel@...uxdriverproject.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH] axi: add AXI bus driver


> The specification for the AMBA AXI Interface is available for free
> download from ARM if you register to their website and accept their license:
> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.set.amba/index.html
> I got it from there without any problems and the license does not look
> too bad for me, by having a quick look at it. I do not know if it will
> help you in any way or if it is completely unrelated.
> 
> Why is the existing support for the amba bus not extended or used in any
> way for this? It exists for some time in drivers/amba/. There already
> was a discussion about this in https://lkml.org/lkml/2011/3/30/186 , but
> with no result as I see.
Existing AMBA bus might is the proper place to publish axi master port
cores but Rafal's implementation manage those internally. Rafal
introduces separate Broadcom-specific bus intended exclusively for
Broadcom-specific devices management. Those devices share common
identification/management techniques which are completely different from
those implemented by other existant kernel buses and amba bus (at least
at it current state) as well. Might be there are good and proper ways to
extend amba bus driver to support axi as well but its a field for guys
and girls confident with closed proprietary arm docs.
Therefore IMHO the bus introduced by Rafal deserves its own driver and
name. But I'm sure that the "axi" tag isn't good one for this bus.

> 
> >>>> Also can't figure out how is this implementation supposed to manage
> >>>> multicore devices.
> >>>
> >>> We have got ideas, but let's first find (wait for) such a device ;)
> >> bcm4716 usb host ? Don't really know if there are any other multicores.
> > 
> > This is SoC, we do not have any problems supporting multiple cores on
> > SoCs. All cores are available at the same time, without any sliding
> > windows.
> > 
> 
> Hauke
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Have nice day,
George


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ